I'd look at the apache logs. I ran into the same problem with an nginx/uwsgi config, and uwsgi's logs pointed me to the fact that I had the wrong group on the application's file permissions.
On Friday, 1 May 2020 18:52:02 UTC+1, Ian W. Scott wrote: > > What are the "likely culprits" I should be looking at when I get an > "Internal server error" accessing admin or appadmin on a fresh web2py > installation? Here's what I've been trying so far. > > - Apache2 config file correctly configured? > - Am I blocking access to admin? > - Is https access configured? > - accessing over https? > - admin password set? > - parameters_443.py file present in web2py folder and accessible? > > I've confirmed that all of these are working properly. (The apache2 config > is identical to one working fine on an identical server.) > > So what else could be blocking admin? What else should I be looking at? > > Thanks ahead of time > > > - newest web2py source, py3.7, apache 2.4 with mod_wsgi > -- 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 web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/d8919438-dec6-4936-98b6-36cb1e446173%40googlegroups.com.
