SignalR errors in console when starting uSync Dashboards
Hi Kevin
uSync Complete 13.1.5
Umbraco 13.3.2
We are getting signalr console errors when starting the usync dashboard.
On my local dev machine I've eliminated errors my enabling web sockets support in local IIS. However, when we deploy to Azure, the error is pretty consistent across all of our environments and apps.
Its probably an azure / websockets thing too (i have seen a couple of posts suggesting maybe a linux azure setup, not sure if your azure is linux or windows?).
but the thing to say is signalr failure will not impact the operation of uSync. the signalR methods are used purely to keep the UI refreshing while the operations happen, and without it, uSync will still perform all the operations and work through any import/export you asik it to do, it will just not update the ui as much (it still updates it a bit).
to be honest this is just me searching, the last few times i've tested it with azure and webservices its been fine. its likey a config setting somewhere, but i am not really sure where.
In fact I'd already worked that one out. However, was wondering more what changed since signalr has always been a part of usync in the backoffice and we didn't see those errors before. We've never had to change the websockets settings in IIS or AppServices before.
To confirm though, setting Configuration>Web Sockets to On in the appservice fixes the errors
Yes in uSync (since v9 and really since v8) I don't think the signalR bit of code has changed much if at all ?
About a year ago, we changed the method to make it a bit more generic with the url not being hardwired into the controller. Github Commit
Three years ago, we had the methods return true, GitHub commit
We do use the already existing signalR client libraries that are part of Umbraco so maybe there was an update there - but i suspect very little changes there appart from the when the .net core version is updated.
SignalR errors in console when starting uSync Dashboards
Hi Kevin
uSync Complete 13.1.5
Umbraco 13.3.2
We are getting signalr console errors when starting the usync dashboard.
On my local dev machine I've eliminated errors my enabling web sockets support in local IIS. However, when we deploy to Azure, the error is pretty consistent across all of our environments and apps.
Any idea what's going on?
Cheers
Jules
Hi,
Its probably an azure / websockets thing too (i have seen a couple of posts suggesting maybe a linux azure setup, not sure if your azure is linux or windows?).
but the thing to say is signalr failure will not impact the operation of uSync. the signalR methods are used purely to keep the UI refreshing while the operations happen, and without it, uSync will still perform all the operations and work through any import/export you asik it to do, it will just not update the ui as much (it still updates it a bit).
for linux on azure this looks similar (with a handshake was cancelled message) https://learn.microsoft.com/en-us/answers/questions/761929/signalr-connection-failure-on-azure-ubuntu-vm
maybe its an azure gatway thing ? https://learn.microsoft.com/en-us/answers/questions/806024/problem-to-receieve-https-trafic-in-azure-applicat
to be honest this is just me searching, the last few times i've tested it with azure and webservices its been fine. its likey a config setting somewhere, but i am not really sure where.
Thanks Kevin
In fact I'd already worked that one out. However, was wondering more what changed since signalr has always been a part of usync in the backoffice and we didn't see those errors before. We've never had to change the websockets settings in IIS or AppServices before.
To confirm though, setting Configuration>Web Sockets to On in the appservice fixes the errors
Regards
Jules
Hi Jules
Yes in uSync (since v9 and really since v8) I don't think the signalR bit of code has changed much if at all ?
About a year ago, we changed the method to make it a bit more generic with the url not being hardwired into the controller. Github Commit
Three years ago, we had the methods return true, GitHub commit
We do use the already existing signalR client libraries that are part of Umbraco so maybe there was an update there - but i suspect very little changes there appart from the when the .net core version is updated.
is working on a reply...