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.
Hi @Kyletest,
Looking at your Nginx configurations, everything is looking great.
You mentioned some of your customers are experiencing 403 Forbidden or 500 Internal Server Error. Usually, when someone is experiencing such errors you can check your WebSerivce’s error log to see what’s going on. Looking at your configuration, I can see the log is located at /var/log/nginx/error.log;.
Having said that, it’s really weird that some customers are seeing 500 Internal Server Error. This is error is usually shown with Apache rather than Nginx. The equivalent to this in Nginx is 502 Bad Gateway.
With that said, seeing the error log should tell you the exact error behind this Error Code and point you in the right direction.
Hello,
The Nginx configuration looks correct. What I could suggest is checking your Nginx error logs to see if you could get some more information on the actual errors that are occurring rather than the generic 403 and 500 errors.
You can check your Nginx error log with the following command:
sudo tail -100 /var/log/nginx/error.log
Feel free to share the output of the log here. Just make sure to remove any sensitive information if there is any.
Regards, Bobby