-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v8.4.4 does not show up as a machine in Windows 11 (Firefox) #287
Comments
Is it possible you didn't wait long enough? You must either pass the account token on the command line or login to your account with a local browser and wait for the browser to actually connect to the local client. Otherwise, the client will not be connected to your account. If you do a full reinstall of the client, i.e. wipe all it's data, then you must do this all over again for that machine. Web Control now pops up a message when it auto links the machine to your account. If you don't see this popup in Web Control after a fresh install or after a reinstall that wipes the data, then the machine is not linked. |
The pop up did not show up until fourth try and only when Edge was used. |
This is where you need to wait. If the browser is already open when you do the client install, it can take some time for it to connect to the local client. I've tried to speed this up but the browser's connection retry logic makes this difficult.
This will not help. As long as the client is not linked to your account you will not be able to see it from any remote machine.
Every time you reinstall you're starting over and only increasing the delay. I think the whole problem here is that the browser takes longer than expected to connect to the local client. The only thing you can do is wait. Reloading the browser or reinstalling will just increase the delays. The only thing that might help is to completely exit the browser and restart it after the client has been installed. Otherwise, the browser's retry logic gets in the way. |
Hopefully this was just my machine which have seen many previous iterations of V8, and maybe Firefox caching, or something. So hopefully it won't happen to new users and those who are upgrading from v7 for the first time, because both of those groups of users won't have account yet. |
So I moved my farm to v8.4.4. Last to go was main PC with Win 11.
Firstly launching installer triggered Windows Defender SmartScreen, which I am not worried about and told it to install anyways. Installation went smooth. After installation web control launched, and I saw other 3 PCs, but not the local one. web control has already logged in, since this PC have seen v8 in previous itterations. Systray icon shows fahlient paused. I can see fahclient.exe in Task Manager. When I click
Fold
through systray icon, nothing happens.Here is the log:
I reinstalled the client few times, reloaded browser page. Nothing.
Ok, now I clicked
Fold
through systray, and it downloaded fahcore_a8 WU. I still cannot see this client neither locally, nor through remote clients (other PCs).This is on Firefox.
I just launched Edge, which I never use, and I can see local fahclient :/
Firefox private browsing still does not see it. In that mode, Firefox is not using any existing cache or cookies.
I logged in to my account through Edge, and pop up showed up saying that client has been linked to an account. And I see all 4 of my machines through edge, however, remote Linux Firefox threw an error:
Loggin in failed. API: error: TypeError: NetworkError when attempting to fetch resource.
After clicking ok, remote PC still cannot see Win11 machine.Reloading remote Linux browser few times finally saw win 11 client.
Local Firefox can also finally see all machines including itself.
I'm not really sure how this can be reproduced and tested and fixed :D This is some weird stuff.
The text was updated successfully, but these errors were encountered: