Mongrel is probably set up to listen on port 3000 for localhost only. Shouldn't you be connecting via port 80 instead and let Apache talk to Mongrel? http://www.myserver.com
On 1/2/07, Jim Douglas <[EMAIL PROTECTED]> wrote:
>From: Steven Lumos <[EMAIL PROTECTED]> >Reply-To: mongrel-users@rubyforge.org >To: mongrel-users@rubyforge.org >Subject: [Mongrel] my apache 2.2 conf >Date: Thu, 21 Dec 2006 11:20:38 -0800 > > >I just finished updating our internal site, which hosts multiple Rails >apps, to Apache 2.2.3. It also has a TWiki rewritten into the root, >ViewVC mounted on /cvs, and /server-status and /server-info. > ><VirtualHost *:80> > ServerName int.example.com > ServerAlias int > > CustomLog /var/www/logs/int.example.com/access.log combined > ErrorLog /var/www/logs/int.example.com/error.log > > [...] > > ## Application Server > > # APP1 > <Proxy balancer://app1> > BalancerMember http://127.0.0.1:11001 > </Proxy> > > Alias /app1 /production/app1/public > <Directory /production/app1/public> > Allow from .example.com > RewriteEngine on > RewriteRule ^/?$ balancer://app1%{REQUEST_URI} [P,L] > RewriteCond %{REQUEST_FILENAME} !-f > RewriteRule . balancer://app1%{REQUEST_URI} [P,L] > </Directory> > # End APP1 > > # APP2 > <Proxy balancer://app2> > BalancerMember http://127.0.0.1:11010 > </Proxy> > > Alias /app2 /dev/app2/public > <Directory /dev/app2/public> > Allow from .example.com > RewriteEngine on > RewriteRule ^/?$ balancer://app2%{REQUEST_URI} [P,L] > RewriteCond %{REQUEST_FILENAME} !-f > RewriteRule . balancer://app2%{REQUEST_URI} [P,L] > </Directory> > # End APP2 ></VirtualHost> > >Then I give mongrel_rails --prefix app<n> and done. Almost too easy. >And it's going to be almost trivial to add more mongrels whenever we >need them and I set up mongrel_cluster. Thanks again Zed and whoever >is responsible for mod_proxy(_balance). > >Steve > >_______________________________________________ >Mongrel-users mailing list >Mongrel-users@rubyforge.org >http://rubyforge.org/mailman/listinfo/mongrel-users I tried this config and can get it working from the server like so, http://www.myserver.com:3000/ ...but when I try to access this address from a client machine elsewhere I get a "unable to connect error" any ideas? Jim _________________________________________________________________ Find sales, coupons, and free shipping, all in one place! MSN Shopping Sales & Deals http://shopping.msn.com/content/shp/?ctid=198,ptnrid=176,ptnrdata=200639 _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users