I have an application that includes a JS client with an ASP.Net server, and is published as an Azure web app.
The application is working smoothly on local environment, however, when browsing to the web app, any PUT request returns with failure - error 500. That's despite the fact that the posted data is indeed saved successfully. Also when remote debugging the web app, the code is executed completely with no errors.
Looking at the diagnostic logs, I can see that the request fails on an IIS module called: ManagedPipelineHandler.
This is the error details:
How can I solve this issue?
If you are seeing HTTP 503 and have enabled Failed request tracing logs, please check the logs for HTTP 503. The one highlighted by you is for HTTP 500. It will give you detailed information as to where the request is failing.
Related
I have .NET Core based backend application (Swagger API) deployed in Azure App Services at https://myapi.azurewebsites.net
It works fine except of one method where I invoke a redirection to another website via GET request in browser as following:
https://myapi.azurewebsites.net/api/Method/Ext&RedirectUrl=https://externalsite.com
The link above shows Error 404 Not Found in a browser and I see that one "/" is missing from the RedirectUrl in IIS logs so this must be the reason:
GET /api/Method/Ext&RedirectUrl=https:/externalsite.com
The IIS error code is the same - 404.
There is no Application Gateway or anything else that can modify the URL.
I checked my App Services instance configuration and did not find any settings that could modify the URL.
Did anyone experience the same issue?
We suddenly began experiencing HTTP 502 errors (The specified CGI application encountered an error and the server terminated the process) from one of the instances of our web app. I was able to determine this using Kudu's "Support" tab whereby you can drill down to metrics per instance.
After restarting w3wp for the instance everything continued successfully as normal. There were no problems with resource usage (CPU/RAM) and the odd thing is that the 502s were returning instantly. So, requests weren't timing out for the client.
What are the possible steps to investigate why this happened?
Our application logs wouldn't have anything and our web server logs only have the record of these 502 but with no further details.
In our case it seems to have come down to port exhaustion on the app service plan. Read here for more details on the limitations for each of the plans available.
I'm trying to host an azure website and tried troubleshooting for a few hours, but still keep getting the same error 502 Web server received an invalid response while acting as a gateway or proxy server.
I tried enabling logging errors on azure, but all it gives me are 404 not found errors
502 errors won't be visible in your IIS logs because they are returned by the front end server which basically fowards the requests to the worker hosting your site and there are many reasons why the front end can return 502 error.
Please follow https://azure.microsoft.com/en-in/documentation/articles/app-service-web-troubleshoot-http-502-http-503/ to troubleshoot the issue and see if you can identify which one you are running into
I had a setup with web servers behind a azure application gateway, some servers works properly and traffic to one of the server is having the 502 issue. So I take the following steps:
Check the Backend health on the application gateway, the server can't be reached.
Open the backend server url on a cloud VM http://hostname, the root website can't be reached. But the http://hostname/app is running.
It turns out the gateway will ping the port 80 of the target machine and somehow I disabled the root website on the target server. So the gateway assumes the server is dead and refused to do the redirect.
We were getting a 502 response with an Azure function. The Function App was started, and all of our functions inside here were marked as "good". But when we checked the azure function process explorer, there were no java proceses (this was written in java... pity me)
When checking the Azure function logs, it turned out that someone had deployed a dynatrace integration and this was crashing the function on startup.
So 502 basically means "I can see you are triggering me but when I try to pass that trigger back to the actual function app, I can't see anything"
I am having an issue getting an HttpClient to work from a Windows Azure website. When running the site from my local machine or a local server it is able to connect to the web services without issue. However, once I publish it to Azure it returns a 404 error from the SendAsync method. I would assume a network problem except that if I do a $.getJSON(...) call to the exact same service from the exact same site I get the response back with no issue. I have tried everything I could think of but am currently out of ideas, has anyone experienced anything like this?
I am having a WCF web service and i am uploading a document to SharePoint site through this service.In my staging server it works fine with a single server but in the production we are having four servers in Load balancing and it is giving me the error...
An error occurred while receiving the HTTP response to http://jai-dms-app.rajdiscoms.com:1111/_vti_bin/Discom/Service.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Please help me ..
The reason why you are having an issue is most likely due to the loop back check. You will need to update the registry to fix that
http://support.microsoft.com/kb/926642/en-us
You may also want to ensure your load balance has sticky sessions