since it's a shared host, are you sure they have port 12003 open for
http requests? usually mongrel is sitting behind apache/nginx which
proxies the requests to the specified port
matte
Tam Kbe wrote:
Thanks Elijah for answer. I thought that might be the problem but
Mongrel will actually start at port 0.0.0.0 unless you expliciatly tell
it to start on 127.0.0.1. Here is output of Mongrel.
** Starting Mongrel listening at 0.0.0.0:12003
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no
restart).
** Rails signals registered. HUP => reload (without restart). It might
not work well.
** Mongrel 1.1.4 available at 0.0.0.0:12003
** Use CTRL-C to stop.
Any other ideas?
Thanks
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
