Rex Tez, Following-up from the above, adding some pointers to isolate the issue.
Based on my understanding, you maybe referring to this doc :Tutorial: Get started with ASP.NET Core SignalR -please do confirm. Which region have you provisioned your Azure resource?
- Please review the URL of the request when 404 occurs. If the URL is targeting to your web app, and similar to
{your_web_app}/hubs/{hubName}
, check if the clientSkipNegotiation
istrue
. When the client initially negotiates with the app server, it receives a redirect URL. It's essential that the client does not bypass the negotiation process when using Azure SignalR - As described in Internals of Azure SignalR Service, Azure SignalR routes incoming client traffics to these server connections. When a server connection is dropped, it closes all the client connections it was serving.
Also, kindly check Service Health and Resource Health status for more info.
- Azure Service Health provides you with a customizable dashboard which tracks the health of your Azure services in the regions where you use them.
- Azure Resource Health helps you diagnose and get support for service problems that affect your Azure resources. It reports on the current and past health of your resources.
Regarding Azure support plans, please check doc: https://azure.microsoft.com/support/plans
Kindly let us know, we will follow-up with you further.