[Mailman-Users] unable to access admin interface

[Chad Rebuck]

thanks for the help

1.  yes, I am able to access the list info page fine, then I click on the
admin interface from that page.  All the pages are http, not https from
what I see.
2. yes
3. yes, I can access other pages on the same server using the same domain
name even when the admin page is not responding.
4. yes, there is a firewall on my router that forwards all port 80 traffic
to the web server
5. I'll have to check on this one.  Will see how to test this, but since i
can get into the admin page and the list info page, etc. does this mean it
must be working?

The display of the admin pages works at times, but then gets stuck and
provides a 504 gateway timeout after choosing a few of the admin page
options.  I can't make any sense of why it stops working.


On Mon, Jul 21, 2014 at 11:29 PM, Stephen J. Turnbull <stephen at xemacs.org>
wrote:

> Chad Rebuck writes:
>
>  > I'm not able to access the admin interface.  I don't reach the page
>  > where I can enter my admin password.  The mailman error log doesn't
>  > show anything.
>  >  I'm running mailman 2.1.18-1.
>  >
>  > This message appears:
>  >
>  > Gateway Timeout
>  >
>  > The gateway did not receive a timely response from the upstream server
> or
>  > application.
>
> This error doesn't indicate a Mailman problem, but rather a network or
> webserver problem.  A timeout indicates that the gateway couldn't
> contact the webserver at all (which is not part of Mailman, but a
> completely separate package).  To check:
>
> 1.  Are you using the correct URL (including port; maybe your Mailman
>     is configured to use https: rather than http: or something like
>     that)?
> 2.  Is there a webserver running on the Mailman host?
> 3.  Is it listening to the port you're using (probably 80 = http, but
>     possibly 443 = https or even something else)?
> 4.  Is there a firewall protecting port 80 (or 443 if you're using
>     https: URLs) between your gateway (proxy server) and the Mailman
>     host?
> 5.  If there is a webserver running, check that it it configured to
>     provide CGI services (lack of CGI should not result in a network
>     timeout, but rather a 404 No Such Page from the webserver, or
>     perhaps a permission failure error -- but you never know).  Still,
>     I'd bet on #2 or #3 here.
>
> HTH
>
> Steve
>
>