My site in opennode.io http://ridezonebd.us.openode.io/ was running fine for 3 days. But today I am getting 502 Bad Gateway when trying to browse.
You can get a 502 HTTP code when your server is no more accessible (either if it has crashed or was stopped). In your case it is due to a lack of credit - in this case we shutdown the running instance.
Related
I made a server with NestJS and ran it on an EC2 instance, and it is responding with 502 randomly.
I googled and a lot of articles mentioned the difference between the timeout interval of ALB and the server.
when I made a simple webpage server with express the same issue happened but fixed it by adjusting keepAliveTimeout and headersTimeout.
(each value was 65000ms and 67000ms)
however, this nestjs server still responds with 502 and I don't know what else to do.
tried to change the timeout of ALB to 30sec and to 120sec and this didn't work either.
what else is the possibility of this issue? I am lost.
we have sails js as an API server and intermittently we are facing 504 upstream timed out the issue, the call was going till Nginx from there its throwing upstream timeout, there is no log coming on the application server, and it is happening across all the APIs intermittently not all the time, and the traffic on server is very low i.e. 5-10 requests per minute and there is no heavy computation going on, so not sure how can I debug this issue. this is a very random issue. also, there are No server restarts or any other errors on application logs. it's running fine on PM2. we are using an AWS EC2 instance. current timeout is 60 seconds but none of our APIs takes more than 500 milliseconds. we are using the node 6.6 version as it is a legacy monolith app so can not upgrade it due to multiple dependencies and no single owner. and requests are passing through the load balancer to NGINX but some time does not reach the application server. also, the instance size is quite bigger in terms of CPU and memory and traffic is extremely low. this is a very random behavior not specific to API. sometimes it can happen 1 out of 10 sometimes 2 out of 5 requests can through a gateway timeout issue.
some of the logs from Nginx are below-
[error] 31688#31688: *38998779 connect() failed (110: Connection timed out) while connecting to upstream, client 10.X.X.X
2022/04/22 16:36:37 [error] 31690#31690: *38998991 connect() failed (110: Connection timed out) while connecting to upstream, client: <server_ip>, server: <DNS_URL>
guys I have tried almost all the things from StackOverflow but nothing helping me, so please help me to find the root cause so I can mitigate the issue
I have azure virtual machine, hosted angular application which is having NodeJs as a backend.
Sometimes it is throwing 502 exception.
If we refresh the page and try to hit the api then we get response. But, sometimes it throws 502 and tells nothing other than this. We tried capturing IIS logs, there also no info about this exception.
Please help me to resolve this issue.
It is Server Side Problem. Kindly check the proxy or ip you're hitting. 502 Bad Gateway Error, which indicates that a server somewhere within the server stack — specifically, one which is acting as a gateway or proxy itself — received an invalid response from a different server.
I am having this strange issue. I am running a node.js, express.js server in Amazon EC2 instance. But when I see my logs there is this log which is originated from my own domain (Elastic IP) (req.ip ::ffff:xxx.174.27.39) and its happening every second. Even if I am idle and not calling the API.
GET /json 404 0.619 ms - 143
GET /json/version 404 1.939 ms - 151
Any idea ? What else I need to share to get help? Sorry I am not a Dev Ops so do not have any good knowledge.
When I publish my app to a Azure Website I get the error on the title and nothing works. It's not temporary.
I researched and looks like it's not related to the problems people have that error have.
I enabled logging but haven't got a much significat otuput.
The log says:
2014-01-15 10:56:26 ~1MANDOOSYSTEM GET /diagnostics/settings
X-ARR-LOG-ID=5632dfdf-9cda-482a-a1d8-e0a9944c8e51 443 - 70.37.162.148
Azure-Portal/3.14.00298.7 - - mandoosystem.scm.azurewebsites.net 200 0
0 463 939 1718
Ideas?
After some trial and error, it ended up being a code error, that would cause a stack overflow if the connection string wasn't set correctly, which wasn't for the cloud.
I would expect to see a more meaningful error while in the cloud since I enabled all the logging features.
Not sure how this works but apparently the server itself was timing out and the other server, the gateway I believe, didn't have a clue on what was up. Just my assumption.