20 messages in com.googlegroups.pylons-discussRe: Having some trouble getting start...
FromSent OnAttachments
walterbyrd22 Jan 2008 08:53 
Mike Orr22 Jan 2008 11:37 
Mike Orr22 Jan 2008 11:40 
walterbyrd22 Jan 2008 14:02 
Cliff Wells22 Jan 2008 19:17 
walterbyrd25 Jan 2008 18:02 
Cliff Wells25 Jan 2008 23:02 
walterbyrd26 Jan 2008 05:15 
Cliff Wells26 Jan 2008 12:20 
Cliff Wells26 Jan 2008 12:31 
walterbyrd26 Jan 2008 16:08 
Chad West26 Jan 2008 18:03 
Mike Orr26 Jan 2008 18:25 
walterbyrd27 Jan 2008 09:04 
Cliff Wells27 Jan 2008 11:05 
Mike Orr27 Jan 2008 11:37 
walterbyrd27 Jan 2008 19:19 
walterbyrd28 Jan 2008 06:38 
Cliff Wells28 Jan 2008 07:00 
walterbyrd28 Jan 2008 08:05 
Subject:Re: Having some trouble getting started with Pylons
From:Cliff Wells (clif@public.gmane.org)
Date:01/25/2008 11:02:59 PM
List:com.googlegroups.pylons-discuss

On Fri, 2008-01-25 at 18:02 -0800, walterbyrd wrote:

On Jan 22, 8:17 pm, Cliff Wells <cl..@public.gmane.org>
wrote:

On Tue, 2008-01-22 at 11:38 -0800, Mike Orr wrote:

It looks like he doesn't have ctypes for some reason (probably Python 2.4).

I have tried going on to the next step, displaying "hello world" with 127.0.0.1:5000 in the URL.

Since I using VPS hosting, I edited the development.ini file to have my actual IP address, instead of 127.0.0.1. But it does not work at all: "can't establish a connection to the server"

Are you trying to connect remotely or from a browser (i.e. links) on localhost? If you are connecting from a remote host, I doubt you'll find port 5000 open by default.

What I would do if I were you:

1) Run pylons on 127.0.0.1:5000 2) Install links or equivalent in your VPS 3) run links (in the VPS) and try to connect to 127.0.0.1:5000

If this works, but you can't connect to real_ip:5000, then I'd think you're looking at a firewall issue. You have three options here:

1) Open the firewall on 5000 (not recommended) 2) Run Pylons as root on port 80 (not recommended) 3) Run a proxy on 80 to pass requests through to 5000 (recommended)

I strongly recommend the third option. Since it's a VPS I'd also recommend using Nginx or Lighttpd as the proxy as they'll use far less resources than Apache (Nginx being my favorite, but either will do).

Regards, Cliff