Hello, Igor. This is what's in the error log:

2011/02/10 10:45:25 [error] 24949#0: *4 connect() failed (111: Connection
refused) while connecting to upstream, client: 205.172.21.53, server:
mulyoo.org, request: "GET /mailman/ HTTP/1.1", upstream: "
http://174.142.104.180:8000/mailman/listinfo", host: "mulyoo.org"
2011/02/10 10:45:25 [error] 24949#0: *4 open()
"/usr/lib/cgi-bin/mailman/favicon.ico" failed (2: No such file or
directory), client: 205.172.21.53, server: mulyoo.org, request: "GET
/favicon.ico HTTP/1.1", host: "mulyoo.org"

I think I may have found the issue though. When I do "telnet 174.142.104.180
8000", I get connect refused. So, I've contacted my hosting company to see
how I can remedy this. Or if you have a suggestion I am all ears (it is an
unmanaged dedicated server).



On Thu, Feb 10, 2011 at 10:52 AM, Igor Sysoev <igor@sysoev.ru> wrote:

> On Feb 10, 2011, at 18:31 , Parker, Joshua wrote:
>
> Hello everyone. I am having a little issue with mailman. I've installed and
> configured mailman for mulyoo.net which works. On this particular server
> the software is Ubuntu 10 (Lucid). On a different server, I did the same
> installation and configuration, but this server is running Ubuntu 8 (Hardy).
> However, when I visit this server (mulyoo.org), I get a bad gateway error.
> Can someone help me troubleshoot and figure out what may be wrong? If it
> helps, I used a tutorial similar to this for installation and
> configuration: http://e-healthexpert.org/book/export/html/430
>
>
> What is in error_log ?
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>


--
Joshua Parker
Church Management System - http://www.churchmember.us/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx