Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Heya all,
An update on an older topic.The error failed (111: Connection refused) while connecting to upstream” suggest an issue with the Application itself rather than the configuration files (Nginx/Gunicorn/etc.).
As such, you’ll always need to review the APP’s error logs rather than your WebServices.
Hi @irfan015,
Make sure to allow Access to port 80, it’s possible your firewall is in the way!
Additionally, usually, such errors that you receive :
502 bad gateway connect() to unix:/run/gunicorn.sock failed (111: Connection refused) while connecting to upstream
This means that there is something wrong with either the configuration for your Nginx Proxy or your Gunicorn app. The one I would bet would be the Gunicorn App. It’s possible somewhere something has not been configured properly. I would suggest seeing if you have configured Gunicorn properly, see if it’s actually listening on any port or if it is at all running.
Hi @irfan015 did you find a solution to your issue? I’m having the same problem