Initial WebSocket connection being stalled for seconds to hours
-
Since about three months, I've had this issue with the initial connection to a WebSocket server on a single site running Pterodactyl being delayed in Vivaldi.
The site is working for all other users (non-Vivaldi), and it's currently* working fine in Firefox too.
Every time a WebSocket connection times out after a few ms to secs (increasing over time), a new one is created which usually also times out.
Screenshot of DevTools:
In this case, it took "only" about 90 seconds, however, 1. that's way too long and 2. it happens again after switching or reloading the page.
The "Queued at" and "Started at" times are the same on every request except the successful one. The "Stalled" time increases over time (seemingly from the start of the connection, so after one hour it increased by an hour) and varies from a few hours (like in this case) to multiple days, highest value I had so far was 12 days.
The issue persists when using a Guest profile, across both stable and snapshot Vivaldi versions, across multiple DNS servers (1.1.1.1, 1.1.1.2, 9.9.9.9, ISP default), and complete Windows resets. After a system restart, the "Stalled" time is randomized, however, without solving the issue.
*I did have some issues with Firefox erroring out socket connections with
NS_ERROR_GENERATE_FAILURE(NS_ERROR_MODULE_SECURITY, SSL_ERROR_RX_RECORD_TOO_LONG)
, though that was shortly after a new cert was issued and hasn't happened since. -
@TomatoCake Hello and Welcome to the Vivaldi Community
No idea about this dactyl thing, but websocket connections work fine in Vivaldi.
The increasing time between retries is normal, that's how network connections work.
Try using an extension that let you test websockets or one of the many sites that do.
https://chromewebstore.google.com/search/WebSocket Test Client
https://www.google.com/search?q=websocket+testOtherwise I guess you'd need to give a sample site and a login if needed.
Please try the troubleshooting steps, including testing in a clean profile and disabling adblocking/extensions:
https://help.vivaldi.com/desktop/troubleshoot/troubleshooting-issues/ -
Hey, thanks for the reply.
As I've said, I've tested using a guest profile, so without any extensions or settings.
WebSockets are working fine on all other sites so I don't think an extension or website would help with this.
How would I provide a sample login here? Sure I can just send it here, but as it's a server control panel, e.g. everyone could change the password of the account.
-
@TomatoCake said in Initial WebSocket connection being stalled for seconds to hours:
WebSockets are working fine on all other sites so I don't think an extension or website would help with this.
The whole point is to test the WS connection to your site using these tools.
As I've said, I've tested using a guest profile, so without any extensions or settings.
Try doing a clean profile of a Standalone install as well.
https://help.vivaldi.com/desktop/install-update/standalone-version-of-vivaldi/How would I provide a sample login here? Sure I can just send it here, but as it's a server control panel, e.g. everyone could change the password of the account.
Doesn't this dactyl thing do read-only accounts?
If so I guess you can send me a chat message and I could have a test here to check if it works on my system. -
@Pathduck said in Initial WebSocket connection being stalled for seconds to hours:
The whole point is to test the WS connection to your site using these tools.
How would those tools help me with that? They won't be able to provide any more debug info.
It's working fine currently, if it happens again I'll try with a standalone install. I'll send a chat message to you soon.
-
To summarize the chat with Pathduck, they were unable to reproduce it and gave me a few suggestions to additionally try.
I just encountered the issue again, and it's happening in my Vivaldi install, Vivaldi Standalone, Chromium Standalone and Firefox (almost unconfigured too). So it's not an issue with Vivaldi but probably with my OS or network...
I've sadly got no clue what to do then, if resetting OS and the router don't help I'm out of ideas - however, I suppose that's out of scope here. If anyone got additional suggestions to try, feel free to suggest them though.
-
@TomatoCake said in Initial WebSocket connection being stalled for seconds to hours:
it's happening in my Vivaldi install, Vivaldi Standalone, Chromium Standalone and Firefox (almost unconfigured too). So it's not an issue with Vivaldi but probably with my OS or network...
Thanks for your feedback.
Good luck for fixing your Network/OS.