I keep getting this 503 error on all my Standard Azure Websites on West Europe.
I've tried restarting the App pool, and also tried scaling down and then up again.
Am I missing something or could it be an error at Microsoft?
We are experiencing the same problem here. I already opened a support ticket and received the following answer:
Thank you for contacting Microsoft Support. This case is related to an
incident currently occurring. We have a team that handles all cases
related to incidents such as this. We will transfer your case to that
team. Once that transfer takes place, here is what you can expect to
happen.
We will send you regular updates on the status of the incident. This information is the same information available from the Azure
Status Page located at
http://azure.microsoft.com/en-us/status/#current. However, instead of
requiring that you check the status page, we will push the information
to you in email.
Once the incident has been mitigated, we will inform you with another notification, after which point your case will be closed.
Now Microsoft is showing the error on its Azure Status website.
Websites in North Europe are working. So we will setup a Traffic Manager on Azure with method "Failover". In case of problems in West Europe the Traffic Manager will automatically route all connections to the mirrored website in North Europe.
See https://azure.microsoft.com/en-us/documentation/articles/traffic-manager-overview/
Related
User reported a failure of one of our Blazor Server apps an hour or so ago. When I investigated it seemed the Azure SignalR service was responding with "502 Bad Gateway" to the initial OPTIONS on the signalr hub negotiation (signalr is separate to the webapp that hosts the site)
In azure manpo, this shows for the SignalR service:
Restarting it does not succeed. Clicking "view activity logs" in the "the resource is ina failed state" banner simply brings a "Code: 'invalidRG'" message
The only significant event recently on this subscription was that it converted from a Free-Trial to Pay-as-you-go and there were some issues transitioning (upgrade done post subscription disable for lack of payment method, took some time to get it reactivated), but then everything seemed to work well for a day
There are many other services in the same resource group, apparently working fine - it's just SignalR. The "Azure status" page shows that all SignalR services are in "Good" condition.
Where does one go from here to diagnose and fix this? Is it a "pay for support from MS and ask them"?
Even though it wasn't a billing issue I wrote on the end of my billing support ticket that I'd raised to get a payment method problem sorted out during subscription upgrade. Support wrote back acknowledging a problem with the Azure SignalR service that was actively being worked on. They claimed that it was already resolved by the time they read my ticket update..
..I don't believe the staus dashboard ever showed AzSignalR as anything other than healthy so it might be that it makes sense to sign up for at least developer support level so there is a route for reporting these things. Either that or (depending on one's moral compass) raise them as billing requests (which are free) if one feels that service availability is a billing related thing (and I suppose it should be; they can't reasonably charge you for services they aren't providing, even if it is only a few cents)
rca in progress
Azure Signal R - Service availability/management operation failures - Mitigated
Resolved: An Azure service issue (Tracking ID 1L_L-NZG) impacted resources in your subscription.
Summary of impact: Between 06:00 and 14:00 UTC on 21 Jul 2021, you were identified as a customer using Azure SignalR Service who may have received failure notifications when attempting to connect or access resources. Additionally, failures may have been seen when attempting to perform service management operations - such as create, update, delete.
We are using Azure Service Bus in the West Europe region.
When I looked in our metrics to investigate a duplicating issue, I noticed that we have a high amount of "server errors". It's nearly 50% of the requests it seems.
Now there is not a lot of information regarding the meaning of server errors by Microsoft, other than saying it's "internal service bus errors" (see https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-metrics-azure-monitor)
My Question:
Do I have to be concerned? Can I still rely on Service Bus in West Europe currently (there were some issues the last month in this region with Service Bus).
What does it mean and how can I solve it?
Thx in advance
I'm following the next tutorial: https://learn.microsoft.com/en-us/azure/azure-functions/functions-twitter-email. I had some problems with connecting to Twitter in Chrome, switched to Edge and was able to make the connection.
However for the sentiment analysis, created earlier in the tutorial, I'm constantly getting, in both browsers, the messages
Please check your account info and/or permissions and try again.
I thought first that it would take a while before the service would kick in gear so I took the same Key1 and went to the API overview from where people can test the service after providing the key. And that worked.
So I'm wondering on how to continue or how to solve the connection problem as the analysis service key works out.
As the time of writing this answer only cognitive accounts deployed into West US region are supported with the logic apps connector. However we are aware that cognitive services recently rolled out a number of new regions for text analytics, and are currently deploying the fix to support other regions. By the end of this week any region should be supported. For now, the workaround is likely best approach (deploy a West US-based cognitive service account).
I had the same issue when trying to login with Chrome.
Edge resolved this case and my resources are deployed in North Europe.
I had the same issue
Please check your account info and/or permissions and try again+text analytics+logic app
when trying establish connection with Text Analytics Cognitive Service from Logic Apps.
I had deleted Text Analytics API and Recreated in Wets US Region and its working fine.
Is there any way to get Azure status update only for some services and regions I am using? For example, I am using Cloud Services in West US. When this service in West US is down, I want to get an alert for it. I don't care about other services and other regions.
If you set up alert notifications for your application, you'll get notified when any of the underlying services you're using are not functioning properly. An alert will ensure that your service is available and working.
https://azure.microsoft.com/en-us/documentation/articles/insights-receive-alert-notifications/
If you get an alert about a service issue, that's when I would first take a look at the Azure status dashboard, and then take a look at your application logs to troubleshoot.
Another trick is to create simple URL's in your application that do a quick service test. For example, let's say you're using blob storage in the west datacenter. You could set up a page that does a test write/read to ensure that service is working. This will give you a 100% accurate indication if there is a problem. Since the cloud is highly distributed, and services statuses don't update immediately, I find this method highly preferable.
You would then point your alert monitoring at URL's like this:
http://yourapp.com/
http://yourapp.com/blobtest
http://yourapp.com/redistest
The Azure Status website has the information your need for all Azure regions.
https://azure.microsoft.com/en-us/status/
I have an Azure service that has been running for a long period of time. It builds a word or powerpoint document based on arguments in the request and returns a uri to the build document. This is access via a visualforce page, when you click a button, it calls the service and displays a link to the document that has just been built. Simple.
All of a sudden, I get an apparently random 503 Service Unavailable error. Sometimes I click the button, no problem. Other times a 503 error. Each time the button triggers exactly the same request. Does anyone know why this might be happening?
Apparently doing the same thing over and over again and expecting a different result, is not insanity!
Thanks for taking the time to read this.
Looking at the monitoring on my service told me the processor was never exceeding 6% of usage, so it couldn't be a lack of resource causing these intermittent 503 errors. It's bizarre and I'm afraid I have no explanation for it, but simply redeploying the cloud service to Azure appears to have done the trick. It now works perfectly. The solution has not changed, so I can only imagine that whatever 'reboot' is necessary after deployment, has rectified whatever the problem was. All I can suggest is that you try the same thing if you are getting intermittent 503 errors.
For me the error went away when I set up auto-scaling. I think failover requests were getting routed to my second VM, and the second VM took some time to spin up because it wasn't ready for the activity. Auto-scaling shut down my second VM and the error no longer appears (I'm assuming it will spin up if/when I get enough traffic to use it).
Hope this also helps someone.
I get this error whenever I create an Azure Function with a storage account in the South Central US. If I use a storage account in a different region the function works.
Try a storage account in a different region than the one you are currently using to see if it resolves your issue.
503 error is simply shows that your application pool was inaccessible, it was intermittent because your application pool is restarting because the lack of resource (processor, memory, etc).
Scale up your instance (Cloud Services or VM) to get more resource for the application pool.