Bad request sent to server during wallet creation

[adidasboy517]

On version 0.1.2. When I upload my keystore for wallet generation and enter the same wallet password as in the Config > Advanced Editor > Validator, I encounter the following error message "Bad request sent to server, something went wrong". Goerli Geth is synced and I've tried two different keystores (remembering the correct passwords). I've cleared the password requirements on each step (8+ char, at least 1 uppercase and 1 lowercase, at least 1 number, and at least 1 special character like !).

[eduadiez]

Could you could add a screenshot of the process and some logs. Has it been an update? WALLET_PASSWORD should be empty and in this version it shouldn't be used. This is my advanced config:

[adidasboy517]

logs-dappnode-package-DAppNodePackage-beacon-chain.prysm-pyrmont.dnp.dappnode.eth.txt logs-dappnode-package-DAppNodePackage-validator.prysm-pyrmont.dnp.dappnode.eth.txt

I tried restarting my NUC, so I think that's why the beacon chain log is showing some issues now, but I was still getting the error even before when the beacon chain log looked good.

[adidasboy517]

here is my browser console error log. I even made a third keystore (carefully typing and retyping and remembering the keystore pw) and uploaded the deposit file to the launchpad and sent 32 goeth to the contract: [https://goerli.etherscan.io/tx/0x849d0fa9ca69a06e26840900711b06a026fabed9172007a84973ed577e4041c5] logs-dappnode-package-DAppNodePackage-beacon-chain.prysm-pyrmont.dnp.dappnode.eth.txt Beacon chain running fine.

[0xtakamaka]

same issue here, using 0.1.3. See details below for further explanation.

Before filing a new issue, please provide the following information. Core DAppNode Packages versions

dappmanager.dnp.dappnode.eth: 0.2.35, commit: cbd7cbcf
core.dnp.dappnode.eth: 0.2.39
vpn.dnp.dappnode.eth: 0.2.7, commit: 12ae223f
wifi.dnp.dappnode.eth: 0.2.4
ipfs.dnp.dappnode.eth: 0.2.11
bind.dnp.dappnode.eth: 0.2.6

System info

docker version: Docker version 18.09.8-ce, build 0dd43dd87fd530113bf44c9bba9ad8b20ce4637f
docker compose version: docker-compose version 1.25.5, build unknown
platform: linux, x64, 5.9.0-2-amd64
Disk usage: 29%

[sinasab]

+1 experiencing the same issue as OP. Interestingly it seems that the failed request is sending the password from the prior form instead of the current one... but that password should also be passing the validation fine, as it also requires numbers/letters/special chars.

Is there a workaround to using your wallet with the prysm validator without going through the web UI in the meantime?

[adidasboy517]

You're correct, it's the webui password (middle pw step between the keystore pw and the wallet password) and it seems to need to be sufficiently complex. I've found that a min of 7 letters (at least 1 uppercase), min of 3 numbers, and 1 special character works. Going down to 6 letters or 2 numbers (sometimes) doesn't seem to work. Hope this helps. I suggest that the min requirements displayed for the WebUI password be updated to reflect this prior to closing this issue.

[sinasab]

I also just discovered this after perusing through the codepath that produced the error.

If you're getting this error, try using a more complicated/long password!

I agree that it'd be useful for the UI to surface the suggestion to use a stronger password. It's confusing otherwise, since the UI only has certain requirements, but the server has stricter requirements.

[0xtakamaka]

And also, do not upload entire "validator_keys" folder into the browser, upload just proper .json file.

It would be awesome if browser would just pop-up console.log messages :).

[muitosabao]

I think I'm having the same issue. How can I do this again? Can I only install the package again and wait for the beacon chain to download again? Or is there a simpler way?

[AVaunt-consulting]

you should be able to go straight to http://prysm-pyrmont.dappnode/onboarding to restart the process

[julienphilbert]

Hello,

Same issue

Any update on this?

Thanks

[0xtakamaka]

Hello,

Same issue

Any update on this?

Thanks

Check 2 things:

• your password should be complex enough
• do not upload entire validator_keys folder, just keys .json