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.
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.
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 have a nodejs app in a ubuntu server. i use plesk for server management.
I am using a url for catching requets from an external api. It sends a webhook to my url for catching information.
I see in my server log, 499 error when this url is requested.
I cannot find any nginx configuration for fixing this problem
Any ideas?
Kind regards
I had similar issues with NGINX recently.
The reason was server timeout - NGINX forwarded request to a backend service (Spring in my case), the backend service timed out.
In my case it was due to "out of memory" exc in Spring Boot app.
So, most probably it's an issue in your node service.
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.
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.