Deployment issue all day to day

Mike O'Neill 1

I keep getting the below error when deploting a web app to azure:
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. (Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED.)

Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists. Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CONNECTION_TERMINATED.
Unexpected end of file has occurred. The following elements are not closed: results. Line 1, position 550. CookieScannerBlazor 0

How do I get round this?

Ryan Hill 26,146 Reputation points Microsoft Employee

2021-10-04T04:39:33.237+00:00

Hi @Mike O'Neill this could be a transient error. How are you deploying your application? What region are you deploying to? Have you tried any other deployment methods?
BhargaviAnnadevara-MSFT 5,456 Reputation points

2021-10-04T04:42:09.773+00:00

@Mike O'Neill Thanks for reaching out. Could you please let us know how you are trying to deploy to Azure? Please elaborate on the steps followed to get here.
BhargaviAnnadevara-MSFT 5,456 Reputation points

2021-10-05T09:53:53.407+00:00

@Mike O'Neill Are there any further details you can provide about the issue?
Mike O'Neill 1 Reputation point

2021-10-05T10:16:52.223+00:00

I was deploying a Blazor Server app, which we have been running successfully live for about 6 months.

I upgraded Visual Studio, which I was using to deploy the app, and the problem seemed to go away, and I successfuly deployed.
However this morning the production app suddenly stopped working, showing repetative 500 errors from the server, presumably SignalR related. It works fine running locally.
If I deploy from another machine, running a previous version of VS, it deploys fine and continues working, but if I deploy from the VC upgraded PC the app fails (with the http statuscode 500 server errors). Am currently stumped, although we can deploy from the older machine.
Ryan Hill 26,146 Reputation points Microsoft Employee

2021-10-05T16:30:41.647+00:00

@Mike O'Neill , just to confirm it seems like you have two separate issues. Your static web app started failing with 500 errors and deploying your code from an upgraded Visual Studio instance results in a deployment failure. But you're able to deploy from a non-upgraded version. Can you include any snippets around HTTP 500 error? Also, what are the two versions of Visual Studio you are using?
Mike O'Neill 1 Reputation point

2021-10-07T20:01:10.917+00:00

Here is the 500 error, you can see it now on scanner.baycloud.com

Request URL: https://scanner.baycloud.com/_blazor/negotiate?negotiateVersion=1
Request Method: POST
Status Code: 500 Internal Server Error
Remote Address: 13.81.122.151:443
Referrer Policy: strict-origin-when-cross-origin

1 answer

Ryan Hill 26,146 Reputation points Microsoft Employee

2021-10-08T19:49:50.34+00:00

Thanks for the additional context @Mike O'Neill . I didn't hit a 500 error but did use browser developer tools and that request makes a call to a SignalR service. You could be running into server connection issues with your SignalR service. Have a look at [this troubleshooting guide](https://learn.microsoft.com/en-us/azure/azure-signalr/signalr-howto-troubleshoot-guide#500-error-when-negotiate-azure-signalr-service-is-not-connected-yet-please-try-again-later] to see if you can better determine the source of the 500. I also came across https://github.com/Azure/azure-signalr/issues/909 which sounds like your situation and is worth look but doesn't have a resolution.
Please sign in to rate this answer.
Mike O'Neill 1 Reputation point

2021-10-09T09:15:13.5+00:00

It looks like it was because we were unknowingly still using the free SgnalR service, which limits the number of messages it processes. we just had to upgrade to a paid version.
This definatly needs a better error notification mechanism!
Sign in to comment