[Mongrel] Mongrel browse problem

Philip Hallstrom mongrel at philip.pjkh.com
Tue Aug 29 23:36:05 EDT 2006

>>> I wanted to show a Rails site to someone so I set up Mongrel and it ran 
>>> fine,
>>> This is my mongrel_cluster.yml,
>>> port: “80"
>>> environment: production
>>> pid_file: log/mongrel.pid
>>> servers: 4
>>> Now, after going back to Apache/Tomcat I can't get the Mongrel site up and 
>>> running again...?
>>> Any suggestions?
>>> (When I run Mongrel, I stop Apache first)
>> How long do you wait after stopping apache before staring mongrel?  I know 
>> some OS's won't let you connect/bind to the same port if it's just been 
>> released... and some OS's have an option to override that behavior... what 
>> happens if you change your port to 81 or something other than 80?
> I was trying to connect on the wrong port...my bad.  It should be 
> www.mysite.com:3000
> Do you know how I can make it so a user can browse 
> http://www.mysite.com/railsemo w/o the 3000?
> I know I can just start mongrel on port 80 and not use Apache, but I need my 
> Tomcat/Apache sites up also.

I don't personally, but Zed always mentions the latest pre-release and the 
--prefix option and something else... search the lists... I'm sure you'll 
find it...


More information about the Mongrel-users mailing list