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
SignalR disconnects Server send events under corporate network (proxies and stuff). SignalR stops conection (long-polling in our case) right after it was established. #4590
Comments
Please provide information about what you're seeing. If your app is at 100% then it might not be able to accept new connections so you might want to fix your app first. |
@BrennanConroy Its working in all regular cases .. 99% cases ..signalr choosing serversentevents , But 1% cases its choosing longpolling as transport , It was connected but immediately closing after 5 seconds ..and its not connecting back again. Its happening only in some customer networks (not every one). using 2.4.1 version now |
Any thing missed here ? , can u reply on my issue |
@BrennanConroy Please update me , what would be the issue here . |
@satish2832 It might help if you could get SignalR traces from the server and the client that is having issues. See https://docs.microsoft.com/en-us/aspnet/signalr/overview/testing-and-debugging/enabling-signalr-tracing Also, are all of your clients doing long-polling? Are they browsers or do you have C#/Java/etc. clients? We also has an issue with long-polling at one point but switching to websockets "fixed" it. What is the CPU and memory load on your server? How many servers are you running? Is there a backplane? Finally, there is a known bug with SignalR 2.4.1 and Chrome that is fixed in 2.4.2. You might want to try to upgrade to it. |
@JGdalevich 99% of users connecting to the serversentevents transport protocol, and very few signalr trying to connect with long polling , But its immediately getting disconnected after 5 seconds .. and no connection establishing with signalr..its only for few users.. Upgraded to 2.4.2 .But facing same issue |
@BrennanConroy Please check this below log [16:09:28 GMT-0500 (Eastern Standard Time)] SignalR: Client subscribed to hub 'chat'. jquery.signalR-2.0.0.js:75 and its bit urgent ,please respond on this. |
@jonathanptew Please check my above logs |
Getting this issue |
Hey everyone, my client is having issues with using SignalR on one of my websites. The site works for other clients but not this one, I assumed it was some kind of firewall/VPN issue (still may be) but it seems to work for some people on their network, but not others. This led me to believe maybe it was something on the local environment, maybe antivirus or something else? Does anyone have any idea what would be causing the client to abort? as I cannot find any details on what causes this to fire. I know it will cause the connection to drop, which is what we are seeing. What could be the issue here ? |
Is this the same error as earlier of a different error? Try getting SignalR traces from the specific client. What kind of client is it and what environment is it running under? |
Here is the trace [16:09:28 GMT-0500 (Eastern Standard Time)] SignalR: Client subscribed to hub 'chat'. jquery.signalR-2.0.0.js:75 |
Those logs make it appear the client stayed connected. Is that not the case? What evidence is there of disconnection. If SSE is problematic, you can just disable it so you don't have the 5 second timeout. |
Hi satish I am also experiencing same behaviour, my webapp is working on customer side but not on my side, did too many R&D & found error signalr calls /signalr/connect /signalr/poll /signalr/reconnect. could you able to resolve this issue ? Please help me if you found any solution |
@JGdalevich @satish2832 @BrennanConroy we also check with ISP for any proxy blocking for that we have bypassed our firewall also but the still issue persists. |
We experience similar behaviour 100% under corporate network (proxies and stuff). SignalR stops conection (long-polling in our case) right after it was established. we are using version 2.4.1
The text was updated successfully, but these errors were encountered: