I have multiple rigs, all in my house, on my lan, all with GUI. I'm using Mint 22, and Nvidia 550.120 drivers along with F@H v 8.3.18, with Brave browser (with shields down). They are all working smoothly and independently without an account.
I created an account per instructions (my words), but when I tried to login I got the error message: "signing in failed > invalid password". I then went through the "forgot password" routine only to get the same "invalid password" message with the new pass phrase. (I am using the four word phrases suggested in all instances.)
My email address must be correct since I'm receiving the F@H password reset email.
Also I have cleared cache and cookies, then tried to reset password again only to have the new password fail, yet again.
Any idea what I'm missing, or what I may need to do to get the folding@home web control set up?
Thanks
Problem logging in v 8.3.18 account
Moderators: Site Moderators, FAHC Science Team
-
- Site Moderator
- Posts: 1273
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: Problem logging in v 8.3.18 account
Please try https://v8-4.foldingathome.org/
It is compatible with 8.3 and has better error checking.
I also recommend beta v8.4.9
https://foldingathome.org/beta/
It is compatible with 8.3 and has better error checking.
I also recommend beta v8.4.9
https://foldingathome.org/beta/
Re: Problem logging in v 8.3.18 account
I upgraded F@H on my primary computer from 8.3.18 to ver 8.4.9 and it is running well and reporting work correctly under my user name.
Creating new account still fails because the account already exists and login attempt still returns "invalid password", (using the four word suggested reset password)
Also noticed several differences between 8.3 and 8.4 such as 8.4 doesn't seem to have the dark mode toggle, and I don't see the work unit ETA info. I understand this is all Beta, so just offering observations.
At this point, I think I'm going to wait for further updates since I am satisfied with being able to process core 24 WU's and all rigs are producing work smoothly now.
Appreciate your time and effort.
Thanks
Creating new account still fails because the account already exists and login attempt still returns "invalid password", (using the four word suggested reset password)
Also noticed several differences between 8.3 and 8.4 such as 8.4 doesn't seem to have the dark mode toggle, and I don't see the work unit ETA info. I understand this is all Beta, so just offering observations.
At this point, I think I'm going to wait for further updates since I am satisfied with being able to process core 24 WU's and all rigs are producing work smoothly now.
Appreciate your time and effort.
Thanks
-
- Site Admin
- Posts: 7988
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: Problem logging in v 8.3.18 account
ETA is still available, but buried a bit. Click on the Work Units tab, then click for Info at the far right for a running WU. The ETA is one of the pieces of information listed.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
-
- Site Moderator
- Posts: 1273
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: Problem logging in v 8.3.18 account
Dark mode and columns in units table became account appearance settings, so now require being logged in.
I have commented that I think they should be stored in the browser local settings, but no word on this. There are much higher priority issues.
I have commented that I think they should be stored in the browser local settings, but no word on this. There are much higher priority issues.
-
- Site Moderator
- Posts: 1273
- Joined: Sat Dec 08, 2007 1:33 am
- Location: San Francisco, CA
- Contact:
Re: Problem logging in v 8.3.18 account
Resetting passphrase worked for me.
I did need to copy the new passphrase and paste it into the login panel, which was still autofilling with the old passphrase.
I also needed to re-link even the local machine, using the gear button for machine settings.
I did need to copy the new passphrase and paste it into the login panel, which was still autofilling with the old passphrase.
I also needed to re-link even the local machine, using the gear button for machine settings.