WebSocket connection to wss:// sub/var' failed: dynamix

[eXorQue]

When I go to the plugins tab, I only get the loading thingy (vertical bars) and then nothing happens. Console shows

WebSocket connection to 'wss://<my-server>:4433/sub/var' failed:

 from

dynamix.js?v=1596576684:34

How to fix this? I'm unable to upgrade my plugins at this moment. 

Edited March 1, 2022 by eXorQue
code-block

[Squid]

Post your diagnostics

[bonienl]

Start with clearing the cache of your browser and restarting your browser fresh.

 

[eXorQue]

Adds diagnostics  Was a bit of a hassle because I didn't have access to the terminal from the web interface because of the wss issue. So had to ssh into it and then scp it from the server.

supermicro-diagnostics-20220304-1001.zip

[eXorQue]

On 3/1/2022 at 8:58 PM, bonienl said:

Start with clearing the cache of your browser and restarting your browser fresh.

 

I have tried clearing cache, and in a fresh install of firefox (as I didn't have it installed yet). In Firefox I see another message 

```
GET wss://488af51abcfd8d6b9afac041cb7eb63e770b2928.unraid.net:4433/sub/dockerload [HTTP/1.1 507 Insufficient Storage 48ms]
```

[Rize]

Did you ever find a solution to this problem? I have the same issue and this seems to be the only thread I can find about it.

[Rize]

For anyone else having this problem in the future (Fix at the bottom, description in the middle):
 

Symptoms: Everything works fine after a reboot but after "extended" uptime (1-2 days) the error would occur and unraid would show 100% memory usage in the "Log" section.

 

Problem: After some days of testing I believe that the issue may be that unraid is unable to handle stale websocket connections. Like when you're putting your computer to sleep the connection doesn't get terminated by your browser since it doesn't actually quit, it just gets frozen.

 

Solution: What fixed it for me was to always log out of unraid, therefore properly closing the websockets, before putting my PC/Laptop to sleep/hibernate.

[zoggy]

just ran into this myself unraid 6.12.10   on firefox 128  (no adblocker enabled)

Firefox can’t establish a connection to the server at wss://192.168.0.100/sub/session,var,notify.

cleared cache+cookies, logged back in.. still nothing.

loaded up chrome  126.0.6478.127, worked fine.

 

went back to firefox, seeing it spamming browser console that it cant get a wss going. then poof started working, refresh paged and all good now. odd indeed.

 

[eXorQue]

For further readers: restarting nginx can sometimes help. At least it did for me. 

Login to the server via ssh (web terminal doesn't work when websockets don't work)

Run the following command. This will restart nginx

/etc/rc.d/rc.nginx restart

 

Or if you don't have ssh access somehow (I haven't tested this, but this is an idea)

Use the `user scripts` plugin and create a script with the command above.

Run the script, and it'll restart nginx, hopefully fixing websockets

 

Edit: hahaha I just saw that I was the original poster years ago! 😂

Edited November 24, 2024 by eXorQue

[jaclas]

A few days ago, this problem occurred to me. I was hoping that the latest update would fix it (6.12.14), unfortunately it didn't. I have a browser log full of error messages:

 

Firefox can't establish a connection to the server at wss://192.168.1.100/sub/session,var,notify. dynamicx.js:15:11951
Firefox can't establish a connection to the server at wss://192.168.1.100/sub/zfs_master. dynamix.js:15:11951

 

I can't access the disks from the GUI either:

 

 

How to fix this? And I'm not asking about manually restarting the server, this is UnRaid's problem and needs to be fixed from within it.

 

Edited December 9, 2024 by jaclas

[VanVanni]

Hi, 

Would love to jump-in on this topic, I ain't a real Unraid user yet and experiencing my options (OMV, TrueNAS and Unraid). Playing with each of them. And I also have the same issue, one of the main reasons to ditch this OS since this is quite unworkable. Unraid was the first OS installed and brand new hardware using the RC build. So this problem seems to occur in Stable and RC. Clearing my browser cache does not seem to help. Creating new sessions by logging in and out does seem to work more often.  

Used:
- Unraid: 7.0.0-rc.2 2024-12-19
- Brave: Version 1.73.104 Chromium: 131.0.6778.204 (Official Build) (64-bit)

- System Arch: x86 AMD

Edited January 5 by VanVanni

[Nirvash]

I wonder why developers never addressed this issue, it's not like it's a rare issue, everyone is encountering this sooner or later. Why? Why not fix it? Or at least say "hey, we know about it and we are taking a look at the issue but it's been hard". All we ever got about this issue is a "post diagnostics" and "refresh browser" 2 years ago.

 

Kinda frustrating ngl.

 

Anyway, does this has anything to do with it?

Edited Sunday at 01:27 AM by Nirvash