[Flask] Debugging "internal server error" with Flask, UWSGI, and Nginx?
Alejo Arias
alejoar at gmail.com
Fri May 6 10:48:54 EDT 2016
Hi Alex,
if the app is not running in debug mode, it won't output any errors on
response.
You can use the logging module and set, for example, a FileHandler to save
all the application errors/warnings to a file or even use the SMTPHandler
to make the app send you and email with the error every time something goes
wrong.
There's good info on how to do this here:
http://flask.pocoo.org/docs/0.10/errorhandling/
Regards,
Alejo
On 6 May 2016 at 16:15, Alex Hall <ahall at autodist.com> wrote:
> Hi all,
> I thought I'd start a new thread, as I've moved to a new step of this
> process. Nginx is working, and I can visit it from another computer, so
> that's great. The problem now is that, though I *should* see my Flask app's
> index page, I instead see "internal server error". No message, no
> traceback, no nothing. The Nginx log has no error in it, making me think
> it's a UWSGI problem. However, /var/log/uwsgi/app/myApp.log is completely
> blank. How would I go about determining the problem? I'm close to having
> this all work, but with no error messages or logs, I'm kind of stuck for
> the moment. Thanks for your patience and help.
>
> --
> Alex Hall
> Automatic Distributors, IT department
> ahall at autodist.com
>
> _______________________________________________
> Flask mailing list
> Flask at python.org
> https://mail.python.org/mailman/listinfo/flask
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/flask/attachments/20160506/bce7b8b5/attachment.html>
More information about the Flask
mailing list