5

personal.unlockAccount(eth.accounts[0],"")

Error: account unlock with HTTP access is forbidden

I run Geth in a Docker container and use

docker exec -it bootstrap geth --datadir=~/.ethereum/devchain attach

to exec the Geth console.

  • 1
    Same problem here, I think it is as a result of some geth update. – Oleg Belousov Apr 9 at 11:07
3

Yes, is some geth update, see more about it here - https://github.com/ethereum/go-ethereum/pull/17037. If you want to enable unlock with opened http (security risk), you can use "--allow-insecure-unlock" option to bypass this protection.

  • Sorry, I am still confused where to append 'allow-insecure-unlock'? – Wayne Apr 9 at 16:54
  • In your case something like: docker exec -it bootstrap geth --datadir=~/.ethereum/devchain --allow-insecure-unlock attach – Artur Iablokov Apr 10 at 9:20
  • It still shows the Error: account unlock with HTTP access is forbidden, why? – Wayne Apr 10 at 15:10
  • try to add "--allow-insecure-unlock" option when you start/run the eth-node. – Artur Iablokov Apr 11 at 9:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.