Sorry if I was not clear enough. It was https that had the problem - it was as though no server existed. The cause was found to be some firewall magic and unrelated to web2py.
I checked http as well because web2py displayed *please visit http://* on the console. I wanted to check if there has been a silent fallback to http. Shouldn't the console message say https instead of http? Will file a ticket. thanks Shivakumar On Mon, Apr 16, 2012 at 11:49 PM, Ross Peoples <[email protected]>wrote: > You can't connect to https using http as the protocol. Getting a "bad > request" message is exactly what happens when you try. So in your browser, > you need to specifically type https://<external_ip>:30000. > > > On Monday, April 16, 2012 1:42:06 PM UTC-4, Shivakumar GN wrote: >> >> Hi, >> >> I am using python 2.5 on Solaris and web2py 1.99.7 >> >> I am trying to get https to work with in built web server as per recipe >> at below link. >> >> http://www.web2py.com/**AlterEgo/default/show/140<http://www.web2py.com/AlterEgo/default/show/140> >> >> I built ssl module built from source since it was missing in python 2.5 >> >> > python web2py.py --nogui -i <external_ip> -p 30000 -c server.crt -k >> server.key >> >> After this, there is no service available via https. On using http, a >> "bad request" message appears in the browser. >> >> This seems similar to issue reported long back, the discussion thread for >> which doesn't seem to have reached a closure. >> http://comments.gmane.org/**gmane.comp.python.web2py/46045<http://comments.gmane.org/gmane.comp.python.web2py/46045> >> >> How to resolve this? >> >> thanks & best regards >> Shivakumar GN >> >>
