-
-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nginx refused to connect and showing bad gateway error. #225
Comments
I seem to have this same problem. I've built a bunch of web apps on this stack in the past and have never gotten this error before...but it's random...most of the time it doesn't work...but occationally it does...I'll do some digging. Nevertheless, thank you very much for this stack! |
I suspect this is caused by the issue raised here: |
I get this iff I set Edit. Never mind, I checked my flask logs and the app was crashing due to a bug in my python script. |
I am working on Nginx, Flask_SocketIO, and uWSGI+Gevent. Whenever I run my code in the docker container I always ended up with a 502 Bad Gateway error. But the flask socketio application runs perfectly in development when I don't use Nginx and uWSGI.
nginx.conf
uWSGI configuration resides in the .ini file.
app.ini
docker-compose.yml
application.py.
requirements.txt
When I build and run
nginx
andztest
docker containers, I am unable to reach my desired endpoint. Nginx gives me a Bad Gateway error. Here are the logs.Please help me to get out of this problem thank you in anticipation.
The text was updated successfully, but these errors were encountered: