Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx Server issue with reverse proxy #554

Open
PunitTailor55 opened this issue Apr 24, 2023 · 2 comments
Open

Nginx Server issue with reverse proxy #554

PunitTailor55 opened this issue Apr 24, 2023 · 2 comments

Comments

@PunitTailor55
Copy link

PunitTailor55 commented Apr 24, 2023

Platform is working fine. I am using same configuration given in setup. My instance is t2.large All of sudden it is giving 504 Gateway Time-out error. I have checked error log of nginx where I have observed that 1220#1220: *2180 connect() failed (111: Connection refused) while connecting to upstream, client: 172.XX.47.61, server: localhost, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8888/", host: "host.com"

Also I have checked nginx status where it is showing,

nginx.service: Failed with result 'timeout'
Stopped A high performance web server and a reverse proxy server.
Starting A high performance web server and a reverse proxy server...

I have added timeout but not working, resstart nginx is also not working. Now application is down. After debug the requests, I have observed that it is websocket issue. I have given timeout proxy_read_timeout in each webhsocket. Sometimes it works.

@eljeffeg
Copy link
Collaborator

Sorry for the delay on this. Were you able to get it resolved? What fixed it?

@PunitTailor55
Copy link
Author

Currently, it is fixed. I have increased the instance size. When the number of users increases, it gives 502 error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants