The issue ended up being uwsgi’s forking. When working with multiple processes with a master process, uwsgi initializes the application in the master process and then copies the application over to each worker process. The problem is if you open a database connection when initializing your application, you then have multiple processes sharing the same … Read more
To fix this I did a few things. – Moved all scripts from the home directory to an /var/www/ – created an www group and www user and chown /var/www to www:www Full Instructions Create a user and group www and www sudo groupadd www sudo adduser www -g www create a dir where your … Read more
HTTP 499 in Nginx means that the client closed the connection before the server answered the request. In my experience is usually caused by client side timeout. As I know it’s an Nginx specific error code.
Run in development mode by setting the FLASK_ENV environment variable to development. Unhandled errors will show a stack trace in the terminal and the browser instead of a generic 500 error page. export FLASK_ENV=development # use `set` on Windows flask run Prior to Flask 1.0, use FLASK_DEBUG=1 instead. If you’re still using app.run (no longer … Read more
When you “run Flask” you are actually running Werkzeug’s development WSGI server, and passing your Flask app as the WSGI callable. The development server is not intended for use in production. It is not designed to be particularly efficient, stable, or secure. It does not support all the possible features of a HTTP server. Replace … Read more