Error : Websocket client error: ConnectionResetError(104, ‘Connection reset by peer’)
Hi all.
I’ve been using TrueNAS on my barebones rig as the main OS for a little while and there is an ongoing issue. i have tried various builds of TrueNAS, but they all suffer the same issue. where TrueNAS would just randomly freeze.
recently, i have updated my router to a Dream Router 7. i have set up vlans and TrueNAS works on the assigned vlan with a static ip from the router. i have installed a 2.5gb NIC and after a fresh install, TrueNAS recognises the NIC and has assigned the IP address.
all works as intended, but randomly TrueNAS freezes or the web portal restarts and i have to re-enter the username and password. when i look at the monitor that the TrueNAS barebones is connected to, there is an error displayed and i can not select anything. so to clear it i have to manually restart TrueNAS.
the error is :
Websocket client error: ConnectionResetError(104, ‘Connection reset by peer’)
i have done the obligatory google search and there is not much on the TrueNAS side of things, mainly docker (which i know nothing about). hens why i have posted here. one thing the AI suggests is check the log file by typing in /var/log/ but it doesnt state where to type that in. so i’ve tried in the “Shell” section of the web portal and i have also tried to do the same in options 7 & 8 of the user interface. but i can not view any logs.
If you are using a Mac (or iPad or iPhone, etc) the only reliable work around I have found is to use a computer with a different OS. Both Linux and Windows seem to work reliably with the browser of your choice. I’ve had some mixed success using a Parallels Linux instance on my Mac but quit using it also because of errors. On the Mac it doesn’t matter which browser you use, whether Safari, Chrome, Firefox, etc. they all seem to exhibit the same problem.
My primary device to connect to truenas, is my windows pc (built by myself). I do have an old MacBook Pro that is on the network, but has not accessed truenas, as in not logged in. Later after work, I will shutdown the MacBook & see if the issue goes away.
You can try it of course but unless you were accessing your NAS with it I don’t expect it will matter that it is simply on the network.
The issue with MacOS (unconfirmed) seems to be a problem with websockets on Macos Tahoe 26 in particular. MacOS 18 was working and presumably ones earlier than that. In a way I’m glad for you, you may have a problem that can actually be fixed without involving Apple or Ix.
I haven’t seen that error with my Windows 11 PC but I don’t use it much for this, my primary clients are a Macbook Pro M2 and x86 Linux (Ubuntu 24 something LTS).
