[Flask] Debugging "internal server error" with Flask, UWSGI, and Nginx?

[Anthony Ford]

Do you have DEBUG set in your app? If not, since you are still in testing,
you should go ahead and enable it.

That should get you the Werkzeug debugger, and help you resolve the problem.

How are you running uwsgi? Supervisor? Systemd?

You can also try running uwsgi standalone on the command line via the
--http option. I find you get a bit more feedback from that, since it
prints messages to the console. Once you have it running there, it should
be easier to get it running behind Nginx, since you know the app already
works.



Anthony Ford,
KF5IBN,
ford.anthonyj at gmail.com

On Fri, May 6, 2016 at 9:15 AM, 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/57e771ff/attachment-0001.html>