Closed MattDHill closed 3 years ago
Hey @MattDHill
Did you reboot bitcoind after changing the rpcpassword?
Yes, and we confirmed using curl that the new creds took. So this appears to be a client issue. Deleting the node from FN and re-adding it appeared to solve the problem.
If you cannot reproduce by just changing your RPC pass, restarting Bitcoind, then editing the pass field in FN, let me know, and I will dig deeper.
@MattDHill I was not able to reproduce this. Only difference is I am working with a local node, I can not test against my onion node as Tor V3 seems to be down again :(
Any chance you can see if this is reproducible on your end with a local node where the address in the FN Node Manger is set to 127.0.0.1:8332
?
Unable to replicate and no further info provided... please reopen if you can replicate.
Describe the bug It appears that changing a node's RPC Password is getting picked up.
To Reproduce Steps to reproduce the behavior:
ThreadRPCServer incorrect password attempt from <host>
The problem can be resolved by deleting the node from Fully Noded, then adding it again with the new credentials.
Device (please complete the following information):