-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
WebSocket is closed before the connection is established. with Win2012 + IIS 8 on Windows Azure. #2780
Comments
Did you figure out why it's failing? I can't tell much from the log other than it threw an exception. Can you try a new app and try to narrow the problem down? |
I have a similar issue, did you find a fix? My issue is here: |
It turn out to be following two issues.
|
@nilangjoshi , Thanks for your hints. Did the two points resolved issue? |
It does. everything seems to be working perfect for us since almost 2 years now. |
This issue has been closed as part of issue clean-up as described in https://blogs.msdn.microsoft.com/webdev/2018/09/17/the-future-of-asp-net-signalr/. If you're still encountering this problem, please feel free to re-open and comment to let us know! We're still interested in hearing from you, the backlog just got a little big and we had to do a bulk clean up to get back on top of things. Thanks for your continued feedback! |
I am facing am issue while deploying the SignalR code to the Windows azure Environment. Please fins the Error Trace at Client Browser as below.
I can also see few errors occurring at the Server Side as Follow
The text was updated successfully, but these errors were encountered: