Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to build crypto.PrivKey #2108

Closed
ASPPIBRA opened this issue Apr 21, 2022 · 8 comments
Closed

failed to build crypto.PrivKey #2108

ASPPIBRA opened this issue Apr 21, 2022 · 8 comments
Labels
kind/bug A bug in existing code (including security flaws) need/author-input Needs input from the original author

Comments

@ASPPIBRA
Copy link

👉️ Please describe what you were doing when this error happened.

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.20.3
  • Electron Version: 17.1.0
  • Chrome Version: 98.0.4758.102

Error

Error: Initializing daemon...
go-ipfs version: 0.12.0
Repo version: 12
System version: amd64/windows
Golang version: go1.16.12
2022-04-21T16:05:46.850-0300	ERROR	cmd/ipfs	ipfs/daemon.go:430	error from node construction: could not build arguments for function "github.com/ipfs/go-ipfs/core/node/libp2p".PstoreAddSelfKeys (github.com/ipfs/[email protected]/core/node/libp2p/libp2p.go:39): failed to build crypto.PrivKey: received non-nil error from function "github.com/ipfs/go-ipfs/core/node".PrivateKey.func1 (github.com/ipfs/[email protected]/core/node/identity.go:18): private key in config does not match id: 12D3KooWJ7NwBpbqBE5Mi3xu4s5AV7fGJmXJHTotwvFB7pKGQb1F != 12D3KooWQzifFh6qXukW7v8H7tL8BvoUjRLdGt24Xm5HQ5NU8FMu

Error: could not build arguments for function "github.com/ipfs/go-ipfs/core/node/libp2p".PstoreAddSelfKeys (github.com/ipfs/[email protected]/core/node/libp2p/libp2p.go:39): failed to build crypto.PrivKey: received non-nil error from function "github.com/ipfs/go-ipfs/core/node".PrivateKey.func1 (github.com/ipfs/[email protected]/core/node/identity.go:18): private key in config does not match id: 12D3KooWJ7NwBpbqBE5Mi3xu4s5AV7fGJmXJHTotwvFB7pKGQb1F != 12D3KooWQzifFh6qXukW7v8H7tL8BvoUjRLdGt24Xm5HQ5NU8FMu

    at errorTemplate (C:\Users\Windows\AppData\Local\Programs\
@ASPPIBRA ASPPIBRA added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Apr 21, 2022
@ASPPIBRA
Copy link
Author

I wish health for those who read this message I performed the intalation of the APP for desktop and made an attempt to recover a node that had done in the first installation of the APP configured by the terminal of my desktop and i went to run the recovery occurred this error. and agorá I can not create a new network node

@hacdias
Copy link
Member

hacdias commented May 5, 2022

Hi @ASPPIBRA @book-s! Thanks for reporting this unusual error. It seems that the keys in the configuration have some mismatch.

  1. Did you use IPFS Desktop before?
  2. Did you already have an IPFS repository? If so, how did you create it?

@lidel have you ever seen such an error? I only found this issue but it is quite old.

@hacdias hacdias changed the title [gui error report] Error: Initializing daemon... failed to build crypto.PrivKey May 5, 2022
@hacdias hacdias added need/author-input Needs input from the original author and removed need/triage Needs initial labeling and prioritization labels May 5, 2022
@ipfs ipfs deleted a comment from welcome bot May 5, 2022
@ASPPIBRA
Copy link
Author

ASPPIBRA commented May 5, 2022 via email

@hacdias
Copy link
Member

hacdias commented May 5, 2022

If you don't have anything important in your IPFS repository, you can just remove it. It should be located in %userprofile%/.ipfs, where %userprofile% is your User's directory.

@book-s
Copy link

book-s commented May 8, 2022 via email

@hacdias
Copy link
Member

hacdias commented May 10, 2022

@book-s i assume the issue is fixed then?

@book-s
Copy link

book-s commented May 14, 2022 via email

@ASPPIBRA
Copy link
Author

ASPPIBRA commented May 16, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/author-input Needs input from the original author
Projects
None yet
Development

No branches or pull requests

3 participants