My azure web app service suddenly becomes unavailable for a few hours.
The app hosts .net core 3.1 web API.
All the requests are pending for a few minutes and then fail. Restarting the app doesn't help. Stopping and starting again too.
Applications insights don't show those failed requests.
Please help, the app serves a lot of users and requests!
I have run Availability and Performance diagnostics at the time of the crash:
Everything looks just fine except the failed requests.
As suggested earlier , you can debug why the web app went unavailable by running the availability & performance under Diagnose and solve problems in the portal.
You can also refer this Azure documentation to troubleshoot Troubleshoot HTTP errors of "502 bad gateway" and "503 service unavailable" in Azure App Service
if you are still not able to find any insights , why the webapp went unavailable you can open a discussion over Microsoft Q&A or please create a technical support ticker by following the link where technical support team would help you in troubleshooting the issue from platform end.
Related
Add or update the App Service deployment workflow configuration from … Build and deploy Node.js app to Azure Web App. My app wont deploy on azure for some reason.
deploy
Deployment Failed with Error: Error: Failed to deploy web package to App Service.
Site Unavailable (CODE: 503)
For a 503 error, I'd do the following:
Start by just restarting the site. If you're getting a 503, it's in a bad state. See what happens.
In the Azure Portal, go to the Web App management blade. Click on Diagnose and Solve Problems. There's lots of utilities and reports that might shed some light.
Go to the Metrics menu. You can check to see if you're suffering from resource exhaustion. Try CPU utilization and memory utilization.
Go to App Service Logs. Turn on Application Logging, Web Server Logging, Detailed Error Messages, and Failed Request Tracing. Failed Request Tracing is particularly applicable for 503 errors.
I'm new to Microsoft Azure. I've created a service which is running in the Azure Portal. See the attached image. I have created a pipeline in Azure and created a release but I keep getting service unavailable see the error below.
> 2020-12-29T12:02:14.3749416Z ##[error]Failed to deploy web package to App Service.
2020-12-29T12:02:14.3769585Z ##[error]Error: Error: Failed to deploy web package to App Service. Site Unavailable (CODE: 503
On the Azure Portal when I click on the URL of my service I also get a service unavailable message. I know it's a free trial I'm running but I checked the status and the credits are still available to use.
Thanks for asking question! The simplest way is to restart your app. On the Azure Portal, on your app’s blade, you have the options to stop or restart your app.
Also, App Service provides an intelligent and interactive experience to help you troubleshoot your app with no configuration required. Access App Service diagnostics, for this navigate to your App Service app. In the left navigation, click on Diagnose and solve problems.
Scaling might be helpful: For more information on scaling, see Scale an app in Azure App Service.
Refer to Troubleshoot HTTP errors of "502 bad gateway" and "503 service unavailable" in Azure App Service
I hosted a Web Api to azure app service. Everything works fine when I published it.
After a couple of days, the Web Api stops responding. But my app service is still running.
Even added application Insight Logs to all the code, to all the catch blocks, even then its not helpful.No exception was logged to date.
Checked the following, but doesn't seem to be helpful.
Thread Count of app service.
CPU time.
and this was the error when I tried to hit from postman after my web API is down.
<html><head><title>500 - The request timed out.</title></head><body> <font color ="#aa0000"><h2>500 - The request timed out.</h2></font> The web server failed to respond within the specified time.</body></html>
When I restarted my app service the web API started working and stops again after a couple of days.
I think your app service is being idled out due to inactivity . Please set always on to be true in the general settings in configuration blade , you can check out link
App service configuration.
We have deployed in Azure Portal some app services under a free plan. The apps seem to be healthy and were working without problems until today. Suddenly all of them are returning an Error 503 "The service is unavailable.".
Under one of the services in Diagnose and fix problems in azure portal I checked CPU, Memory, Port usage and everything looks healthy.
Any ideas on how to fix the issue?
Could that be Microsoft maintenance and after some hours the sites are working normally again?
After 5 hours the services were up again. Probably it was a maintenance issue. So after no indication that my services have a problem, waiting some hours was the solution. Maybe this site that displays the azure status could be helpful for those that run into this problem.
Our website has been hosted on Azure for a few years. Tonight it is throwing 503 Service unavailable errors. I cannot even load a url to a .jpg file. I have restarted the app and still nothing loads from the website. I cannot buy Azure support because I have bought and cancelled Azure support in the past. We are a 3 person business and depend on our small website and it is down and I don't know what to do. None of the trace logs make any sense to me.
I think 503 could mean that you reached a quota and Azure now respond with a 503 for requests. So I would check the Quotas section within your App Service Plan.
Also check:
Troubleshoot HTTP errors of "502 bad gateway" and "503 service unavailable" in Azure App Service
There are several things you can do to help remedy the situation.
Restart the application (please indicate what it is that will help
us)
Restart the instance that the application is running on.
Restore from a previous working backup of the site.
You should also add more information to your post so we can help, like what application you are using e.g. Apache, Nginx ect.
I've also had a similar problem. I had two deployment slots and in the first slot (production) which I had the latest code and in the second slot, I've missed deploying the latest code and configured traffic as 60-40 which gave me hard time finding it.
Once I've set 100% to the production slot it started working.
Just thought to share this in case it could be useful if you come across the same stuff in the future.
For me it was "Path mappings" in "Configuration".
As soon as i added a new Azure Storage Mount, the application broke.
Setting my Storage account -> Networking, to "Enabled from all networks" fixed the issue.
For us it was a result of the remote debugger. Disabling remote debugger and restarting the app service fixed the 503 error. I think one dev was remote-debugging while another was deploying the app and that seems to have caused an issue under the hood of the app service that broke port binding (we were seeing a stack track in logs about failing to bind to port).