OK, I got some more replies from the very prompt people at webfaction. The problem seems to be with my app (web2py).
"... This is how the server works, HTTP is port 80 SSL is port 443 Your app runs on port 10853 locally and is than proxied by nginx to either port 80 or 443 http://docs.webfaction.com/user-guide/_images/inside-the-server.png ..." Yet, I most definitely have a file called parameters_443.py. Any clue, or pointer? Thanks On Sep 27, 3:33 pm, MidGe <degreef.mic...@gmail.com> wrote: > yes, I think along the same line. In my communications withwebfaction, > howeveer, I have not been able to get an answer yet, > beyond 443 or the port assigned when creating the app. > > I can only presume that no one has usedwebfactionwithuwsgifor a > web2py installation. I think I may have to put this one under the "Too > hard.. " basket and look for another project. Grrr! > > Life is too short at my age! :) > > On Sep 26, 9:02 pm, Vasile Ermicioi <elff...@gmail.com> wrote: > > > > > > > > > > Do you mean the port for https as a standard wold-wide(?), atwebfaction, > > > web2py,uwsgi? > > > the default for https is port 443 > > > perhaps this is a question forwebfactionsupport, > > > my thoughts: > > I think this is a different port assigned when you click 'https' on app > > creation > > and so http requests are going to custom_port and https to a another one, in > > case of Johann 3031
