Re: easy n00b question

> >> Totally not your fault, I wen't through the
exact same problems when I
> >> started with CP. This is exactly the problem I
feel cp's docs have,
> >> information like this is hard to find if you
don't know where to look
> >> and it's not mentioned in the tutorial (or
linked to for that matter).
> >> Unfortunately I don't have the time to fix it
myself.. :-(
>
> I found that you need to set the ip address of the
machine in the
> configuration. Unlike 2.1, where  you could set
127.0.0.1 as the ip
> address in CP and you could access it externally using
the machine's ip
> address, in 3.0.2 you need to set the ip address of the
machine in the
> global configuration. This opens up CP to external
access (don't ask me
> why, but at a guess it's security related).
>
> ip_address =
socket.gethostbyname(socket.gethostname())
> global_conf = {'server.socket_host' : ip_address}
> ...etc

I had this exact problem too where a stock 2.1 worked for
me, but 3.0
didn't. On my Mac, this was due to IP6 being enabled and
cherrypy
binding to an IP6 socket. That's why specifying an IP4
address makes
it work. I created a ticket here: http://www.cherryp
y.org/ticket/711

I agree with the ticket responders that it's not a bug; but
I still
think an info msg at startup would be helpful when
getaddrinfo()
resolves to more than one address. A lot of people don't
know the
consequences of having IP6 enabled (which it is by default
on Mac OS).
True, that's the users' responsibility, but why make
experimenting
with CherryPy that much harder when a simple change could
help them
debug the issue? It's easy to get frustrated when the
tutorial samples
won't work out of the box, and hurts the chances of the
project
getting a wider audience.

So I also agree that better docs in general would be really
helpful.
(Maybe if I get some time I will volunteer myself soon,
though I'm
very much a n00b...) I write this msg because I think
CherryPy is
pretty awesome, I use it and like it a lot, so I want to see
it used a
lot more.

Jeff


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---

jeffcodefork wrote:
> I had this exact problem too where a stock 2.1 worked
> for me, but 3.0 didn't. On my Mac, this was due to IP6
> being enabled and cherrypy binding to an IP6 socket.
> That's why specifying an IP4 address makes it work. I
> created a ticket here: http://www.cherryp
y.org/ticket/711
> 
> I agree with the ticket responders that it's not a
bug;
> but I still think an info msg at startup would be
helpful

Makes sense. I just added a warning about 'localhost' to
the
CherryPy checker.


Robert Brewer
fumanchuaminus.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---