Hi list,
I'm trying to serve a Flask app on Debian 8, with the eventual goal of
using Nginx to serve the app through UWSGI. For now, though, I'm just using
UWSGI. I'm pretty new to Debian, web server stuff, and UWSGI. About the
only thing here I'm not new to is Python. I have a background in computers,
but I've never tried something quite like this. I should also say that I
have only SSH access to the Debian machine, as it's a VM on Google Cloud.
I'm using a Windows computer to access the Debian one, with SSH for direct
access and Firefox to test web serving. Unfortunately, I can't copy text
from SSH output to paste here, nor can I paste into SSH. Any output you ask
for I'll have to copy by hand, so forgive any mistakes.

Here's where I am right now. I've gotten the chdir and venv options
correct, I think, and fixed the errors. At least, when I run the app by
supplying all the options in the call, it seems to be okay--no errors or
warnings. However, Firefox on Windows sits there for a minute, then times
out. My log is completely empty, and when I access the "site" on Firefox, I
see nothing written to stdout. Of course, I specify a logto in my ini, but
still, that log remains empty. Either way, it's like UWSGI doesn't even
know it's being asked to supply something.

I've run this with
sudo uwsgi --socket 0.0.0.0:5005 --protocol=http --chdir ...
and
sudo /etc/init.d/uwsgi start --socket...
and it doesn't seem to matter which one I use.

I'm stumped. Mostly, I can't find where to go to see what errors, if any,
are being written. Is the problem some kind of implicit IP limiting I don't
know about, or something equally hidden? Is there a way to view errors? Can
I put UWSGI in a special "debug" mode? Speaking of which, yes, my Flask app
is in debug mode, but it doesn't even get that far. Thanks in advance for
any help.

-- 
Alex Hall
Automatic Distributors, IT department
[email protected]
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to