Web Control not connecting. [was various]

[bikeaddict]

Merged 3 separate topics on the same problem - j

The machines tab isn't listing anything that's currently running. Browser console shows responses of NS_ERROR_CONNECTION_REFUSED, NS_ERROR_NET_RESET, NS_ERROR_TIMEOUT or NS_ERROR_UNKNOWN_HOST.

The Work Units tab still shows WUs, but they are from Feb 15 or older.

[bikeaddict]

Seems to have started hours ago. Perhaps monitoring of this server needs improving.

Code: Select all

07:45:38:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
08:10:37:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
08:17:59:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
08:33:29:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
08:54:47:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
09:34:47:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
09:37:02:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
10:12:12:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
10:18:49:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
10:36:55:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
10:41:21:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
10:53:18:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:01:41:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:09:24:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:23:39:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:26:04:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:28:23:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:30:42:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:33:01:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:40:12:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:46:28:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:52:40:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
11:58:35:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
12:00:49:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
12:03:04:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
12:05:19:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN
12:10:58:I1:Account websocket closed: NONE msg=Connection failed: error=EOF code=HTTP_UNKNOWN

[Albuquerquefx]

I'd suggest posting this in the "Issues with a specific server" subforum here: viewforum.php?f=18&sid=0fbe777e32c44562b414fe78cfc53a67

[HandOverFist]

V8 5.5 not showing all clients, running or not. This has been a recurring problem for some time now. At one point uninstall/reinstall would remedy this, but now has no effect.

I have V8 5.5 installed on five different machines atm with only one actively folding. The active machine shows the client running on it's own monitor, but I can't see it on any other machines/monitors. At he moment one of my machines is showing a client highlighted that is not even active, but not showing the machine that is actually active highlighted. All other machines are shown listed greyed out. In other words, I can only see active clients on a monitor that is connected to that individual machine...nothing remote.

[Albuquerquefx]

I have four Folding clients in my house: my physical Windows-based gaming rig, two physical Fedora 43 rigs, and a virtual machine with a GPU passed-thru running Ubuntu 22.04 LTS. Normally I keep tabs on them all using my phone to log into and view the native client: https://v8-5.foldingathome.org/machines. This morning, all machines are "disconnected" from my phone's ability to view them.

I sat down in front of my gaming rig, and it was A: logged in and B: could only see itself, saying all other machines were disconnected.

I sat down in front of one of my Fedora physical machines, and it was A: NOT LOGGED IN, and B: could only see itself. I logged in again, and then went through the logs to find when I was "logged out." Funny thing: it doesn't look like I was ever logged out; all my WU's back as far as I wanted to scroll (eg last night when I know it was working) were pulling WUs for my user name and team. Thus, the core folding process knew who I was, but the web client did not. Also, even after logging in, I could not see any other machines.

Third physical Folding machine was the same as the other physical folding box: said I was logged out, couldn't see any other machines. I logged it back in, checked logs to confirm all WUs had been pulling down without issue under my proper name and team. It still can't see any other machines after logging in.

Finally my Ubuntu Folding VM was "fine" in that it thought I was still logged in and was still working, but couldn't see any other machines.

So, right now as of this writing (8:55am CT, February 18th 2026) none of my web clients can see other machines, but seem <?> to be processing work units without issue. There have been no network changes to my Fortigate in the last month; there are no DNS interruptions, there are no internet routing changes (to at least the 3rd hop out from my dmarc), there have been no OS or browser patches applied in the last seven days, and all of these machines can see / talk to eachother without issue. It also doesn't seem to be server-specific because units continue to be assigned, downloaded, and uploaded without issue.

This issue affects my modern Samsung Android phone running Chrome, my gaming rig (Windows 11-dot-current) running Edge, two Fedora 43 boxes running Firefox, and an Ubuntu box running Firefox (the Ubuntu box runs F@H as a docker container.) It's not just one browser, or just one OS, or just one machine / hardware type issue.

[eutaxy]

This problem showed up for me only this morning. I am running v8.5.5 on both Linux and Windows hosts. The https://v8-5.foldingathome.org/machines page shows only the local host; other hosts are shown as "No resources Disconnected". The problem seems browser-independent: I tested with Firefox, Chromium, and Edge. Restarting a "Disconnected" host does not fix the problem.

[goodyca]

I am seeing the same thing on three Fedora 43 computers. It started this morning. I upgraded all three machines yesterday morning, and I had no issues seeing all three machines after the upgrades yesterday. I am running fah client version 8.4.9.

[muziqaz]

fah node is struggling

[muziqaz]

fah node is struggling

[muziqaz]

fah node is struggling

[Joe_H]

The developer is looking into the problem, no ETA at this time.

[HandOverFist]

Appears to be working now.