CODEWITHSUNDEEP
asp.netazureweb-applicationssignalr
Bibber
Bibber

Reputation: 51

SignalR negotiate fails (Bad Gateway)

Someone any idea, I’ve been struggling with this for some time.

I'm using SignalR (Asp.net 5). when I try to debug local (ISS 10.0 express) everything is working fine. SignalR is working (Long poll).

Now when I publish the app to Azure it I can access : .azurewebsites.net/signalr/hubs

but I cannot access .azurewebsites.net/signalr/hubs/negotiate it returns: The specified CGI application encountered an error and the server terminated the process.

When my web app calls $.connection.hub.start() it will fail. GET XHR http://xxxx.azurewebsites.net/signalr/negotiate [HTTP/1.1 502 Bad Gateway]

I’m running out of idea's. Don't know how I can get more debug information.

Small selection of my ‘already tried’ list:

EDIT: Now getting more details on this error:

CryptographicException: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.

Still absolutely no idea how to solve this!

Upvotes: 3

Views: 2004

Answers (1)

Bibber
Bibber

Reputation: 51

Solved by using appBuilder.UseAesDataProtectorProvider(); (from Owin.Security.AesDataProtectorProvider;)

I have no idea if this is the best solution.

Upvotes: 0

Related Questions