Today’s development colleagues read the data from PostgreSQL and wrote it to excel. Due to the large amount of data, the development colleagues wrote the code that was not good enough and the speed was too slow, so there was a problem. I found the following information and modified the configuration of nginx to solve this problem. The detailed errors are as follows:
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check theerror log for details.
Faithfully yours, nginx.
Solution:
Change localhost in nginx configuration file to IP
Or
Modify the hosts file and add 127.0.0.1 localhost
location/{
proxy_pass http://localhost:8080 # change to 127.0.0.1
}
Set connection time
proxy_ connect_ timeout 300; # The connection timeout between nginx and back-end server (proxy connection timeout)
proxy_ send_ timeout 300; # Back end server data return time (proxy sending timeout)
proxy_ read_ timeout 600; # After successful connection, the response time of back-end server (proxy receiving timeout)
is shorter
After modifying the configuration file, reload the configuration file
nginx -s reload
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)
- Solutions to nginx upstream timed out (Two Situations)
- There are a lot of no live upstreams while connecting to upstream about nginx logs
- Solve the 400 error of nginx forwarding websocket
- [Solved] nginx upstream timed out (110 connection timed out)
- [IOS series] -A server with the specified hostname could not be found. Problem solved
- Nginx error 111: connection rejected [How to Solve]
- Nginx normal user startup configuration error: && springboot-swagger & Unable to infer base url
- PHP nginx 504 gateway timeout gateway timeout error