with some testing I managed to find a cause to it, though i am not sure why.
To summarize. i had not changed Apache configuration since install. (Debian stable) The application was running without a problem. I then did some updates to the application on my local machine and pushed them up to the server via the admin interface. The updates where just new pages. Nothing much different from what was already being used and working in the application. With your mention the error maybe in Apace config. I checked my configuration against the one in the Web2py book , my only difference was that i had the ServerName and Alias set as my domain name. i removed these and it functioned. So that was the problem. I am not sure why it would work for so long if it was incorrect or what in the upgrade i did that would call this configuration to suddenly cause a problem. Thanks for the help guys. This was a tricky one for me. On Thursday, February 26, 2015 at 4:39:31 AM UTC-8, Leonel Câmara wrote: > > I think this is probably a webserver (probably apache) configuration > issue. Have you made any changes to the configuration recently? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
