Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure SignalR Service Connection is not active - 1.0.0-preview1-10264 #324

Closed
YoupHulsebos opened this issue Jan 7, 2019 · 4 comments
Closed

Comments

@YoupHulsebos
Copy link

I updated our signalr packages from 2.4.0 and added RunAzureSignalR instead of RunSignalR. Added this code in de Startup.cs

app.Map("/signalr", map => { var hubConfiguration = new HubConfiguration { EnableDetailedErrors = true }; map.RunAzureSignalR(typeof(Startup).FullName, hubConfiguration, options => { options.ConnectionString = AppApiSettings.SignalRServiceConnectionString; }); });

But when I try to send a message to the hub I get an exception:

The connection is not active, data cannot be sent to the service.

Can't find any reason this would happen or why the service would not run. When I use RunSignalR (self hosted) everything runs great.

Any help would be greatly appreciated.

@vicancy
Copy link
Member

vicancy commented Jan 8, 2019

Could you enable trace as similar to

GlobalHost.TraceManager.Switch.Level = SourceLevels.Information;

to see if any error reported when establishing server connections?

@YoupHulsebos
Copy link
Author

YoupHulsebos commented Jan 8, 2019

Sure thing. The complete log is attached here: log.txt

Seems it does error on making the connection to the signalr service:
Failed to start connection. Error starting transport 'WebSockets'.
Microsoft.AspNetCore.Http.Connections.Client.HttpConnection Error: 11 : Exception thrown: 'System.Net.WebSockets.WebSocketException' in Microsoft.Azure.SignalR.AspNet.dll

@vicancy
Copy link
Member

vicancy commented Jan 8, 2019

Yeah, can you repro it locally? you can try the steps in #279 (comment) to view the exception details.

@YoupHulsebos
Copy link
Author

Thanks! Turns out it was the exect same error: TLS2.1 was not enabled on my .net472 solution. The same solution in that ticket fixed my issue. Maybe an idea to add this to the docs as an reminder for people on .net framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants