Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Save the file.
Restart BOINC.
When prompted, leave both options blank. Hit OK.
or
Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Press Enter once on the line the key was on.
Save the file.
Restart BOINC.
When prompted, leave both options blank. Hit OK.
or
Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Make your own password here. Minimum 6 characters.
Save the file.
Restart BOINC.
When prompted, type localhost and the password you just saved. Hit OK.
Well, much to my amazement, stopping boinc, modifying the password in the gui_rpc_auth.cfg file to a random string of alphanumeric characters of the same length, then restarting boinc did in fact correct this problem. I didn't even need to enter the password when I started boincmgr. Any explanation as to why it didn't like the (seemingly) random string of characters originally in that file would be appreciated.
modifying the password in the gui_rpc_auth.cfg file to a random string of alphanumeric characters of the same length
Heh, that's one I never heard of before. But, if you added characters outside the hexadecimal range (0-9 and a-f), then it's now just a 32 character password.
modifying the password in the gui_rpc_auth.cfg file to a random string of alphanumeric characters of the same length
Heh, that's one I never heard of before. But, if you added characters outside the hexadecimal range (0-9 and a-f), then it's now just a 32 character password.
You can't assume anyone asking questions here knows anything about how the internal workings of BOINC are implemented. I somehow overlooked the "32 character hexidecimal key" part of your instructions. I assume based on your apparent amusement that it is a randomly generated 128-bit key. When reading your instructions I assumed that entering my own password would be safer than setting the contents of gui_rpc_auth.cfg blank but I wonder now if leaving the contents blank would cause it to generate a new random 128-bit key (I guess I'll have to try that and see).
One note about your instructions. I found that after I modified the gui_rpc_auth.cfg file (entered a password) I was no longer prompted when I entered boincmgr. In other words, boincmgr connected to the localhost automatically without any action on my part after I changed the contents of the file.
Errr.... have we covered/mentioned that each BOINC installation needs to know the name or IP address of the computer from which it is going to receive GUI/RPC calls? This is contained in a text file called 'remote_hosts.cfg' in the BOINC install folder/directory. It may need to be created, and could even refer to the self/same computer.
Cheers, Mike.
( edit ) Another possible source of mischief is firewall settings/activity relating to the IP ports 1043 and 31416. Potentially a complex issue.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Exit BOINC. Edit your
)
Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Save the file.
Restart BOINC.
When prompted, leave both options blank. Hit OK.
or
Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Press Enter once on the line the key was on.
Save the file.
Restart BOINC.
When prompted, leave both options blank. Hit OK.
or
Exit BOINC.
Edit your gui_rpc_auth.cfg file and take out the 32 character hexadecimal key you find inside it.
Make your own password here. Minimum 6 characters.
Save the file.
Restart BOINC.
When prompted, type localhost and the password you just saved. Hit OK.
Well, much to my amazement,
)
Well, much to my amazement, stopping boinc, modifying the password in the gui_rpc_auth.cfg file to a random string of alphanumeric characters of the same length, then restarting boinc did in fact correct this problem. I didn't even need to enter the password when I started boincmgr. Any explanation as to why it didn't like the (seemingly) random string of characters originally in that file would be appreciated.
Thanks.
RE: modifying the password
)
Heh, that's one I never heard of before. But, if you added characters outside the hexadecimal range (0-9 and a-f), then it's now just a 32 character password.
RE: RE: modifying the
)
You can't assume anyone asking questions here knows anything about how the internal workings of BOINC are implemented. I somehow overlooked the "32 character hexidecimal key" part of your instructions. I assume based on your apparent amusement that it is a randomly generated 128-bit key. When reading your instructions I assumed that entering my own password would be safer than setting the contents of gui_rpc_auth.cfg blank but I wonder now if leaving the contents blank would cause it to generate a new random 128-bit key (I guess I'll have to try that and see).
One note about your instructions. I found that after I modified the gui_rpc_auth.cfg file (entered a password) I was no longer prompted when I entered boincmgr. In other words, boincmgr connected to the localhost automatically without any action on my part after I changed the contents of the file.
Errr.... have we
)
Errr.... have we covered/mentioned that each BOINC installation needs to know the name or IP address of the computer from which it is going to receive GUI/RPC calls? This is contained in a text file called 'remote_hosts.cfg' in the BOINC install folder/directory. It may need to be created, and could even refer to the self/same computer.
Cheers, Mike.
( edit ) Another possible source of mischief is firewall settings/activity relating to the IP ports 1043 and 31416. Potentially a complex issue.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal