Hi! Following is my nginx error.log. I tried to solve this by following this suggestion,https://unix.stackexchange.com/questions/717952/tcp-timeouts-in-nginx but it didn’t change the limit it’s still 1024. How do I resolve this issue? Any suggestions would be greatly appreciated!
GNU nano 7.2 error.log
2024/07/09 16:42:51 [alert] 15364#15364: *6 open socket #7 left in connection 3
2024/07/09 16:42:51 [alert] 15364#15364: aborting
2024/07/09 17:15:12 [alert] 16519#16519: *236 open socket #20 left in connection 5
2024/07/09 17:15:12 [alert] 16519#16519: *17 open socket #7 left in connection 6
2024/07/09 17:15:12 [alert] 16519#16519: *49 open socket #8 left in connection 7
2024/07/09 17:15:12 [alert] 16519#16519: *239 open socket #23 left in connection 14
2024/07/09 17:15:12 [alert] 16519#16519: *220 open socket #21 left in connection 16
2024/07/09 17:15:12 [alert] 16519#16519: *241 open socket #24 left in connection 18
2024/07/09 17:15:12 [alert] 16519#16519: *244 open socket #27 left in connection 20
2024/07/09 17:15:12 [alert] 16519#16519: aborting
2024/07/09 17:15:49 [error] 16540#16540: *2 upstream prematurely closed connection while reading response header from upstream, client: 24.193.166.172, server: outdoors.rest, request: "GET /api/membership HTTP/1.1", upstream: "http://127.0.0.1:5050/api/membership", host: "outdoors.rest", referrer: "https://outdoors.rest/"
2024/07/09 17:15:49 [error] 16540#16540: *2 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 24.193.166.172, server: outdoors.rest, request: "GET /api/membership HTTP/1.1", upstream: "http://[::1]:5050/api/membership", host: "outdoors.rest", referrer: "https://outdoors.rest/"
2024/07/09 17:15:54 [error] 16540#16540: *2 no live upstreams while connecting to upstream, client: 24.193.166.172, server: outdoors.rest, request: "GET / HTTP/1.1", upstream: "http://localhost/", host: "outdoors.rest"
2024/07/09 17:15:55 [error] 16540#16540: *2 no live upstreams while connecting to upstream, client: 24.193.166.172, server: outdoors.rest, request: "GET /favicon.ico HTTP/1.1", upstream: "http://localhost/favicon.ico", host: "outdoors.rest", referrer: "https://outdoors.rest/"
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!
Heya @swimminglapiswalrus,
Can you check your application logs to see if there you see any errors? This seems to be a bit odd to be honest. So, yeah please check your application’s error logs and see if you can see anything out of the ordinary there.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.