Nginx server is loved by many people for its proxy capabilities and ease of configuration. A simple proxy_pass
can allow you to connect to any of the backends such as GoLang, php-fpm, NodeJS, another Nginx, Tomcat, Apache, Gunicorn, uwsgi, Flask, Django, an external CDN and many more.
When proxying a request to another server, you may or may not have access to a log of the server. So it is important to be able to debug the problem if an issue occurs. Common problems that you may face when proxying request are below
- 502 Bad Gateway
- 504 Gateway Timeout
- 404 Page Not Found
- 403 Access Denied
- 400 Bad Request request header or cookie too large
- Wrong Redirect
- upstream sent too big header while reading response header from upstream
- Primary script unknown while reading response header from upstream
- upstream prematurely closed connection while reading response header from upstream
Continue reading