get "Node connection failed! Check username/password" when trying to open primary wallet

[pla7a]

When I try to open my primary wallet I get an error message saying "Node connection failed! Check username/password". I have tried connecting with 15+ different public nodes and all return the same error. I have also tried connecting over different internet services (different WiFi and cellular data).

When creating a new wallet, things work fine and it is able to connect. I tried showing "secrets" so I can restore fresh but there is no way to locally retrieve the secrets, it also requires connection to a node.

[Using Android 9 with Monerujo Version 1.15.3 'Dark Fork (5030)]

[m2049r]

The issue seems to be that the cache file is corrupt, so there are two solutions to this:

• use a backup
• delete the wallet cache file (see instructions below) - note that this will also delete all your notes & private transaction keys (which you may need prove sending) but since that cache file is corrupt i guess there is no other choice.

let me also note, that this issue is monero-inherent since v0.17.1 (seems to happen when syncing to a broken node) and not monerujo-specific.

How to find & delete the cache file

Connect your phone to your PC or use a file explorer app and locate the monerujo folder and make a backup copy of your wallet files from your phone's storage, just in case. There should be three files per wallet:

• walletname
• walletname.keys
• walletname.address.txt

Delete the file that has no extension, i.e walletname. Open Monerujo again.

Let me know if this works - please leave the issue open as the error message is stupid in this case and needs fixing.

[tomatensaus]

Got the corrupt cache too. Can confirm that deleting the file above solves the issue. Second time in the last couple of days. Rather annoying. Error message could also be better than "Node connection failed! Check username/password"

Spent hours thinking that there was something wrong with my node

[kn0wmad]

Same issue, fix here worked, many thanks @m2049r! That was very aggravating

[Forage]

Had the same issue. The work-around did the trick. It would be good to have the wallet detect the issue itself and start over automatically (after having warned about the massive time it'll take), if corruption itself can not be prevented somehow to begin with.

[Engelberg]

I am getting this error after updating to the latest version of monerujo. I know you made changes to the wallet file storage in this most recent version. Were you expecting the update to corrupt the cache and thus break the wallet's ability to connect to nodes?

Where does monerujo create backups of the cache to restore from? I have my crazypass, since that is supposed to help with the restore process.

[m2049r]

monerujo doesn't create backups by itself. the cache file gets corrupted for yet unknown reasons. if you feel it was ok before the upgrade, i suggest you make a zipfile with the wallet.keys & wallet files and import that as a new wallet.

create a backup from time to time in case this happens again. beware the wallet is actually encrypted with the crazypass so make sure you have that written down in addition to your seed.

if you don't care about the cache (i.e. don't care about notes, subaddress names, etc) you can "reset wallet" which erases the cache altogether and rescans from scratch.

[Engelberg]

So the wallet.keys and wallet files sitting on my phone are actually an older version of the wallet data than whatever corruption the program is currently seeing? Because if those are the same files the program is using, which are corrupted, than I don't see how importing them will solve anything.

[Edit] I checked the timestamp and the Wallet file is indeed a couple months older, which is encouraging from the perspective of getting back to a working state. So which is the file that got recently corrupted?

[Engelberg]

As per your instructions, I created a zip file out of those two files, and moved it to my google drive so I could import it. The "import wallet" ui lets me navigate to google drive, but it doesn't see the zip file, and if I do a search to force it to show the zip file, it won't let me click on the file to import it.

I then tried putting the zip file on my phone's SD card. In this scenario, the UI lets me navigate to the zip file, but when I click on the zip file it just takes me into the zip file, and shows me the two individual files, and I have no option to select them.

[Engelberg]

Figured out how to select the zip file rather than navigating into it, and did the import. Still getting the node connection error :(.

[wincak]

I could get this error several times in the row like this:

0. Clean install or wipe app data+cache
1. Recover wallet from seed
2. Open the wallet, let the sync begin
3. Click "street mode", enter password
4. Close the wallet, wait for the "wrapping up" to finish
5. Try to open the wallet again

The error goes away by resetting the wallet (or wiping app data+cache).

I'm using current version 2.0.6 (10060) from F-Droid on LineageOS 15.1

[Forage]

Can this issue be (partially) node related as well? Maybe try not insisting on using the same node but try a different one instead.

[d4f5409d]

The issue seems to be that the cache file is corrupt, so there are two solutions to this:

• use a backup
• delete the wallet cache file (see instructions below) - note that this will also delete all your notes & private transaction keys (which you may need prove sending) but since that cache file is corrupt i guess there is no other choice.

let me also note, that this issue is monero-inherent since v0.17.1 (seems to happen when syncing to a broken node) and not monerujo-specific.

How to find & delete the cache file

Connect your phone to your PC or use a file explorer app and locate the monerujo folder and make a backup copy of your wallet files from your phone's storage, just in case. There should be three files per wallet:

• walletname
• walletname.keys
• walletname.address.txt

Delete the file that has no extension, i.e walletname. Open Monerujo again.

Let me know if this works - please leave the issue open as the error message is stupid in this case and needs fixing.

If this is node related then your node gotta be broken bro