Paste the SSH command you created that tunnel - I think the error is in that.
On Mon, Aug 24, 2009 at 07:05, DenesL<denes1...@yahoo.ca> wrote: > > While running tests using SSH tunnels to connect a machine running > web2py to itself, I noticed that the variable hosts in admin/models/ > access.py does not include the IP address which was used to start > web2py, only 127.0.0.1 and the machine's host name. > > An example of the connection is: > > client machine ---> port22: web2py machine : port x ---> port 8000 : > same web2py machine > > where the web2py machine is also running the SSH server which > establishes the tunnel to port 8000. > request.env.remote_addr has the IP address of the web2py machine, not > 127.0.0.1, so the connection is deemed insecure and rejected. > > Is there any reason not to have the web2py machine IP address in the > hosts in access.py?. > > Denes. > > > -- Álvaro Justen Peta5 - Telecomunicações e Software Livre 21 3021-6001 / 9898-0141 http://www.peta5.com.br/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
