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

error from node construction: failed to listen on any addresses #2148

Closed
DaveSchmid opened this issue May 18, 2022 · 4 comments
Closed

error from node construction: failed to listen on any addresses #2148

DaveSchmid opened this issue May 18, 2022 · 4 comments
Labels
kind/bug A bug in existing code (including security flaws) need/author-input Needs input from the original author

Comments

@DaveSchmid
Copy link

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

Specifications

  • OS: win32
  • IPFS Desktop Version: 0.20.6
  • Electron Version: 18.0.3
  • Chrome Version: 100.0.4896.75

Error

Error: Initializing daemon...
go-ipfs version: 0.12.2
Repo version: 12
System version: amd64/windows
Golang version: go1.16.15
2022-05-18T14:25:51.641 0200	ERROR	cmd/ipfs	ipfs/daemon.go:430	error from node construction: failed to listen on any addresses: [listen tcp4 0.0.0.0:4002: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig. listen tcp6 [::]:4002: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.]
Error: failed to listen on any addresses: [listen tcp4 0.0.0.0:4002: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig. listen tcp6 [::]:4002: bind: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.]


    at errorTemplate (D:\Programme\Netzwerk\IPFS\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:78:49)
    at Object.loadWindow (D:\Programme\Netzwerk\IPFS\IPFS Desktop\resources\app.asar\src\daemon\migration-prompt.js:115:26)
    at startIpfsWithLogs (D:\Programme\Netzwerk\IPFS\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:163:25)
    at processTicksAndR
@DaveSchmid DaveSchmid added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels May 18, 2022
@hacdias
Copy link
Member

hacdias commented May 19, 2022

Hi @DaveSchmid!

I couldn't find any specific information about this error online, but it seems that either:

  1. Port 4002 is already being used by another process. Do you perhaps have another instance of IPFS running, or a different process using port 4002?
  2. There is some permission restriction not allowing IPFS to use that port. Perhaps there is some firewall or antivirus restricting the access to the port. Another option if you're using a Windows machine within some organisation is that there may be restrictions regarding which ports you can use.

Original Error: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
Likely English Error: An attempt was made to access a socket in a way forbidden.

@ipfs ipfs deleted a comment from welcome bot May 19, 2022
@hacdias hacdias added need/author-input Needs input from the original author and removed need/triage Needs initial labeling and prioritization labels May 19, 2022
@hacdias hacdias changed the title [gui error report] Error: Initializing daemon... error from node construction: failed to listen on any addresses May 19, 2022
@DaveSchmid
Copy link
Author

netstat -a says port 4002 is not in use.
Windows Defender Firewall is disabled on all profiles.
But you're right it's not a problem of IPFS Desktop, it's a problem of Windows or Windows Firewall. It's sometimes a bit complicated with Defender and the automatic network detection. Especially with a heavily used developer PC and automatic updates of Windows and IPFS and all the 1000 things..

But you shouldn't change the title here. It's the title that made the error dialog automatically. I just pressed the button to report bugs. Because it was such a pretty button..

@hacdias
Copy link
Member

hacdias commented May 22, 2022

But you shouldn't change the title here. It's the title that made the error dialog automatically. I just pressed the button to report bugs. Because it was such a pretty button..

The title is hard-coded for any error that happens within IPFS Desktop. It is good to change the title so we can find possible duplicates in the future.

@DaveSchmid
Copy link
Author

then maybe you should change that to a dynamic title in the code.

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

2 participants