[gui error report] Error: Initializing daemon...

[rtxs34]

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

Specifications

• OS: linux 6.1.0-17-amd64
• IPFS Desktop Version: 0.33.0
• Electron Version: 19.1.9
• Chrome Version: 102.0.5005.167

Error

Error: Initializing daemon...
Kubo version: 0.26.0
Repo version: 15
System version: amd64/linux
Golang version: go1.21.6
2024-02-04T20:48:58.836-0300	ERROR	core	core/builder.go:158	constructing the node: could not build arguments for function "github.com/ipfs/kubo/core/node".PeerWith.func1 (github.com/ipfs/[email protected]/core/node/peering.go:30): failed to build *peering.PeeringService: could not build arguments for function "github.com/ipfs/kubo/core/node".Peering (github.com/ipfs/[email protected]/core/node/peering.go:14): failed to build host.Host: received non-nil error from function "github.com/ipfs/kubo/core/node/libp2p".Host (github.com/ipfs/[email protected]/core/node/libp2p/host.go:40): failed to listen on any addresses: [listen tcp4 0.0.0.0:4001: bind: address already in use listen tcp6 [::]:4001: bind: address already in use listen udp4 0.0.0.0:4001: bind: address already in use listen udp4 0.0.0.0:4001: bind: address already in use listen udp6 [::]:4001: bind: address already in use listen udp6 [::]:4001: bind: address already in use]
Error: constructing the node (see log for full detail): failed to listen on any addresses: [listen tcp4 0.0.0.0:4001: bind: address already in

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[lidel]

Duplicate https://github.com/ipfs/ipfs-desktop/issues/2216