Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>> 
Due to the modification of the server configuration on the upstream, Max is added_ fails,fail_ The three parameters of timeout and weight result in a large number of errors of the following types in nginx error log.
First of all, the problem is related to the client. The client is accessed by HTTP. Then, the problem is that there is a problem in the connection and interaction between nginx and the back-end API. After checking the configuration of nginx, there is no problem in the configuration
Looking at the explanation of the error, we can get the result that there is no server that can provide services in the upstream. However, I can directly access the back-end server, which proves that the server is available
Finally, find the document, and find that the problem is that the business requires to keep the session, but nginx does not keep the session to the API. Of course, nginx can not find the back-end available server, and it will report no live upstream
Modify the configuration of nginx
Similar Posts:
- Nginx Timeout Error: upstream timed out (110: Connection timed out) while reading response header from ups…
- [Solved] Nginx proxy Timeout: upstream timed out (110: Connection timed out)
- Nginx error 111: connection rejected [How to Solve]
- Visit the back-end application through nginx and report an error err_ CONTENT_ LENGTH_ MISMATCH
- [Solved] Nginx 502Bad Gateway: some static resources cannot be accessed
- [Solved] Nginx reverse proxy 502 permission denied
- nginx: [error] open() “/usr/local/nginx/logs/nginx.pid“ failed (2: No such file or directory)
- Fix Nginx 502 Error:upstream sent too big header while reading response header from upstream
- Nginx an upstream response is buffered to a temporary file,nginx502 Error
- HTTP status code 499 [How to Solve]