An Error occured while making HTTP Request from POSTMAN - azure

This Error Occurs While I am trying to make any HTTP request to my REST API on Azure server from POSTMAN.
Why is this occurs ?

Might be your machine was started but you forgot to start the Azure server. I once faced the same problem, it occurs because my server was not properly started

This error occurs due to the tcp/ip request. This indicates whether you have not started your virtual machine or you your api needs a token to access

Related

IBM Domino 502 Bad Gateway on redirect

In our application we have a REST integration with another service
It worked fine untill recently, however, sometimes we are returned with 502 Bad Gateway in the application
We send HTTP requests through curl and it seems that to be working but then we are presented with the error I described above
The client is believed to have a firewall installed
Whenever we face the problem, I usually ask the administrator to turn this thing off and it does the trick but I'm not sure whether it has something to do with the code?
My question is what causes such behaviour and how to avoid it in the future?

502 Exception - Azure Virtual Machine

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.

newman running on gitlab timed out with 503

I have made a newman collection for some calls. One of those call is to call a flask server, I also have a .gitlab-ci file to configure all the tests, all of them run perfectly until today. It wasn't able to call the flask server from gitlab, instead it takes around 1 min and timed out with status code 503. Locally seems working fine. I also try to make curl calls directly to the ip address and it returns the response. Any ideas on why this could happen? What could be changed either from newman side or gitlab side? Don't know if this is related to the proxy issue.
I would search on the receptor side. Because you are geting a valid response code (503) as a response. So the connection to your flask server seems to exist in principle. If you are using your flask server as a gateway, you must check the connection between flask an the other service.

411 content length required on IIS server but not on linux based server

I have a RESTApi application which I have recently moved over to Microsoft Azure App-services. Earlier it was hosted on a Linux server. The issue that I am seeing is weird:
When a client using ASP.net call a POST request with no body and no content-length header explicitly passed, the request fails with 411 Content-length required error. For the same client, the requests which were going on to the Linux server are still working fine.
For a client using python/PHP, the same request works on both the IIS and Linux environments.
I am unable to understand why this might be happening. I have resolved the issue by sending content-length:0 for this API call but want to understand why this is happening.

499 error code with nginx plesk for nodejs app

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.

Resources