search

FoldingAtHome / fah-web-client-bastet

Folding@home client frontend
GNU General Public License v3.0
20 stars 9 forks source link

Remote computers not seeing each other, initially #215

Open jon-ault opened 1 week ago

jon-ault commented 1 week ago

I have two computers running 8.4.9 (one Windows, one Mac) and one Windows computer running 8.3.18. None of the web clients can see any of the other computers, each one can only show its own status with the other two grayed out. Screenshot 2024-11-21 at 1 21 08 PM

jcoffland commented 1 week ago

Are you logged in? You cannot see remote machines unless you're logged in.

jon-ault commented 1 week ago

Yes, logged in on all machines. Also, when logged out the other machines simply don't appear at all; I have to be logged in to see the greyed out sections for those computers.

muziqaz commented 1 week ago

Does Mac have some sort of software firewall? Are you using firewall on Windows machines?

muziqaz commented 1 week ago

Yes, logged in on all machines. Also, when logged out the other machines simply don't appear at all; I have to be logged in to see the greyed out sections for those computers.

FAH is account based. You have to be logged in to see remote machines.

jon-ault commented 1 week ago

Yes, the Mac has a built-in firewall. It wasn't causing any issues with 8.3, and turning it off does not fix this issue in 8.4.

As for being logged in, the screenshot above was taken while logged in on all computers.

jon-ault commented 1 week ago

OK this is interesting. If I leave the browser running long enough untouched it eventually connects to the other computers. I'm not sure how long it takes, something on the order of 15-20 minutes. I'll try to time it.

jon-ault commented 1 week ago

It took about 4 minutes for the other machines to appear, so I was way off in my initial estimate. Screenshot 2024-11-21 at 2 32 09 PM

muziqaz commented 1 week ago

yeah, it seems Firefox is not the favorite browser for FAH :)

That's probably related to this: https://github.com/FoldingAtHome/fah-client-bastet/issues/287 above moved to the following issue: https://github.com/FoldingAtHome/fah-web-client-bastet/issues/214

kbernhagen commented 1 week ago

Similar problem on macOS Brave browser. JS console has repeated ~5x error

WebSocket connection to 'wss://node1.foldingathome.org/ws/account' failed: WebSocket is closed before the connection is established.
jcoffland commented 1 week ago

These are different issues. One is about the local client taking a long time to show. This issue is about seeing remote clients.

jcoffland commented 1 week ago

Was this issue also caused by not being on the correct Web Control page?

kbernhagen commented 1 week ago

I was using the correct v8-4 web page. Brave, Safari, mobile Safari are all working normally right now.

kbernhagen commented 1 week ago

I considered it a similar issue because you mentioned web control would abort connections early to avoid browser connection fall off in another issue.

And I was experiencing delay connecting to remotes via node. This was the correct issue.

jon-ault commented 1 week ago

Was this issue also caused by not being on the correct Web Control page?

I don't think so, I'm using the url "https://app.foldingathome.org/" on my Mac which redirects to "v8-4.foldingathome.org". But something has changed in the last couple of hours because now it immediately shows all the computers with no delay.

muziqaz commented 1 week ago

I think this is just initial loading. After that, I never had issues in my case

jcoffland commented 1 week ago

I considered it a similar issue because you mentioned web control would abort connections early to avoid browser connection fall off in another issue.

This is only with the local client connection. Web Control connects directly to the local client when possible. The remote connections are all via fah-node. There's only a delay if you have problems connecting to fah-node which usually only happens when your Internet connection goes down. fah-node itself is on Amazon AWS and has a very high up time.

kbernhagen commented 1 week ago

Then what was causing WebSocket is closed before the connection is established

jcoffland commented 1 week ago

That's the Websocket to the local client.

kbernhagen commented 1 week ago

No. It was a node connection. WebSocket connection to 'wss://node1.foldingathome.org/ws/account' failed: WebSocket is closed before the connection is established.

kbernhagen commented 1 week ago

The local client connected immediately. Remotes did not. I figured you modified the deployed Web Control or fah-node when it started working again.

jcoffland commented 1 week ago

I didn't modify anything.

bollix47 commented 1 week ago

The problem is back today after working fine overnight and this morning .... i.e. can see local machine but not the remote ones

kbernhagen commented 1 week ago

Web control v8-3 seems to have the same problem. I don’t have an older client running right now to test against that.

muziqaz commented 1 week ago 
Firefox can’t establish a connection to the server at wss://node1.foldingathome.org/ws/account. 
The connection to wss://node1.foldingathome.org/ws/account was interrupted while the page was loading.

This is while I have the tab open with all the clients shown as loading, even the local one. I have not reloaded the tab since I launched it

bollix47 commented 1 week ago

my remotes have now shown up .... a half hour after I tried to load the page .... a reload showed all cients again after a slight hesitation

jcoffland commented 6 days ago

I think this may be a problem with fah-node. There may be some sort of leak. It had been running for a couple of months. The memory usage before the restart seemed a little high. I restarted it and things started moving again.