Hi there, If I disable the https requirement for the admin, I will not be able to get into the admin area either.
The strange thing is that I can log in. The system recognizes my password as valid (when it is, and not when it is not) but it does get me back to the login screen, in an endless loop. Secondly when I can get it to the edit mode in admin, any attempt at saving a file gets me a "communication error". Where is the best place to get some help about this. I am still fairly certain that it is a uwsgi issue that may be related to using the --https option for built-in server use. Any clues? Thanks for any help... Deadline looming and if this doesn't get resolved soon, I may have to change horses and very regretfully abandon web2py so late in the piece, as it shows tremendous promises if it could actually get going. I am happy to try anything and give whatever information may help resolve this but I am not sufficiently well versed with uwsgi to find a way to start investigating. On Oct 2, 6:22 pm, Roberto De Ioris <robe...@unbit.it> wrote: > Il giorno 02/ott/2011, alle ore 10:17, MidGe ha scritto: > > > I suspect the problem must be with uwsgi. > > > The reason I say that, is that if I use the apache as per install script, > > it works. > > > If I stop apache and setup uwsgi, everything exactly the same, I have the > > problem. I can access the site. login even, but I get in a loop showing me > > back to the login screen when trying to access admin area. Killing uwsgi > > and restarting apache.. everything hunky dory! > > > I suspect that using uwsgi, and specially the built-in server option sort > > of messes up the users. > > > Any ideas? > > Have you tried disabling https-requirement for the web2py admin interface ? > > If it works the problem is clear and bypassing it to make webfaction happy > would be easy > > -- > Roberto De Iorishttp://unbit.it > JID: robe...@jabber.unbit.it
