Just ran into this one, but with apache, so a little followup - this was a case where you're trying to establish an SSL connection, and other side expects a regular http request. It had nothing to do with the actual port or self-signedness of the cert - just mismatching the virtualhost directives so the https ended up being served with the wrong entry. So, if you get this error, try http:// instead of https:// (you can't have both http and https on the same port anyway) or fiddle with https settings.
On Nov 5, 7:29 pm, airdrummer <[EMAIL PROTECTED]> wrote: > > What happens if you try getting web2py to bind to port 443 instead of > > socket.error: (13, 'Permission denied') > > because ports<1024 are privileged --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
