Hey Gents,
When I run the app locally, targeting a local db, Signal R works. However, I just recently pushed to Azure web services with a sql db. Everything seems to be working good with the exception of signalR. See attached errors.
Thanks for your help in advance.
Josh
5 Answer(s)
-
0
Hi,
Do you use Azure websites or do you have a Virtual Machine on azure ?
-
0
<cite>ismcagdas: </cite> Hi,
Do you use Azure websites or do you have a Virtual Machine on azure ?
Azure Websites.
-
0
Hi,
Have you seen this forum topic #1891@de6bfba4-df3a-40f8-a554-b893cc8ca062 ? You can try this workaround <a class="postlink" href="https://github.com/SignalR/SignalR/issues/3670">https://github.com/SignalR/SignalR/issues/3670</a>.
-
0
I found a solution that seems to be working - the solution is referenced here: <a class="postlink" href="http://stackoverflow.com/questions/36475209/signalr-2-fails-on-azure">http://stackoverflow.com/questions/3647 ... s-on-azure</a>
To fix this, I added a reference to Owin.Security.AesDataProtectorProvider (NuGet package) and then added app.UseAesDataProtectorProvider() in ConfigureOwinServices() right before app.MapSIgnalR();
using Owin.Security.AesDataProtectorProvider; ... namespace App.Web.Startup { public class Startup { private static void ConfigureOwinServices(IAppBuilder app) { app.Properties["host.AppName"] = "App"; app.UseAbp(); app.UseAesDataProtectorProvider(); app.MapSignalR(); } } } -
0
Thanks @leop,
We alrady implemented in AspNet Zero. Thanks again :)
