Okay, I'm narrowing down what the problem might be. The site is presently
using webfaction's shared SSL certificate for https, which browsers don't
recognize as secure. Could that be causing the admin interface to throw the
500 error?
On Thursday, April 30, 2020 at 3:02:58 PM UTC-4, Ian W. Sc
Unfortunately I don't know anything about nginx. I've always worked with
apache2. Can anyone suggest how to debug this? I'm really at the end of my
rope here.
On Thursday, April 30, 2020 at 10:37:58 AM UTC-4, Ian W. Scott wrote:
>
> Thanks very much
>
> Ian W. Scott, PhD
> Associate Professor of
Thanks very much
Ian W. Scott, PhD
Associate Professor of New Testament
Tyndale Seminary, Toronto, Canada
www.ianwscott.com (http://www.ianwscott.com)
Paul's Way of Knowing: Story Experience and the Spirit (Baker Academic [Mohr
Siebeck], 2006)
The Online Critical Pseudepigrapha (SBL, 2006-; pseu
Hi Ian,
I do have a copy of the script, it's a bit old, but I'll attach
it anyway, maybe it's of help.
Kind regards,
Annet
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list
Thanks Annet for your help. Webfaction doesn't seem currently to make that
install script available when you're creating a new application in a
server. Web2py doesn't appear anywhere on the list of available application
types. Do you know if it's available somewhere else on their service?
Thank
Why didn't you use the web2py install/unstall script that webfaction
provides?
It installs web2py served via nginx and uWSGI.
The script mentions 2 caveats:
Web2py won't work properly if it is mounted to a sub-URL like
http://domain.com/web2py/. Instead, it must be mounted to the
website root, e
6 matches
Mail list logo
