This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Relay is not working #3716
Labels
effort/hours
Estimated to take one or several hours
kind/bug
A bug in existing code (including security flaws)
kind/resolved-in-helia
need/analysis
Needs further analysis before proceeding
P2
Medium: Good to have, but can wait until someone steps up
0.6.1
(WSL) Microsoft x86_64 x86_64 x86_64 GNU/Linux
(MacOS) Darwin Kernel Version 20.4.0
Guess it's about
js-libp2p
,ipfs-core
Severity:
Medium?
Description:
Relay is not working
Steps to reproduce the error:
according to this ipfs-core usage (https://github.com/ipfs/js-ipfs/tree/master/examples/circuit-relaying#so-what-just-happened)
ipfs-core
and nodejs,ipfs.create
withrelay: { enable: true }
, relay is not working either.await ipfs.swarm.addrs()
/p2p-circuit
Update
I found out that if the
repo
is created by$ jsipfs init
, then it'll have the/p2p-circuit/
but if it's created by ipfs-corethen the relay will not work, the relay.enabled seems not the point.
Update 2
Guess the root cause is the jsipfs get the
p2p-circuit
slowly, so only the daemon one has the p2p-circuit, and if I create the repo in app, then I'll not have the p2p-circuit address immediately...Update 3
Also the
$ jsipfs daemon
not always get the/p2p-circuit
Sometime attached circuit-relay in few seconds, sometimes still not have
/p2p-circuit/
in few minutesThe text was updated successfully, but these errors were encountered: