Closed on-meetsys closed 1 year ago
This module is not being actively developed any more and is very out of date.
Looking at the error, it's failing to decode the protobuf as it's being sent a message that's missing the publicKey
field. In v4 of libp2p-pubsub-peer-discovery
this was marked as required though also proto3 which is weird because required
is not in the proto3 spec. In later versions it's a singular field so this error would not occur.
I would start by upgrading all of the deps here to the latest versions, though our maintenance time is limited so you may be better of forking for now.
I'm going to close this issue because this repo is not maintained any more.
I need a relay server for my project, to allow p2p clients to discover themselves if they are behind NAT or firewalls (my project works perfectly with
mdns()
on a local network). I have therefore installed ajs-libp2p-relay-server
on a server (8000 and 15003 ports opened), and I start libp2p nodes on clients with the setup described on js-libp2p-pubsub-peer-discovery page. The nodes run the most recent libp2p : "^0.42.1-9a6022b7" I bootstrap the nodes with the multiaddresses given during thejs-libp2p-relay-server
start.Then, I have the following error on the relay-server :
this error only occurs when there is the webSockets() transports. If not, there is no error, but the relay-servers sees nobody (no node discovery...). If I force the client to connect to the relay-server, with :
on the client side, then the relay-server seems to be unreachable :
May be this is due to the fact that this
js-libp2p-relay-server
is 3 years old and uses an older libp2p lib "^0.32.3" ?But I've not found any other project to build a relay for the
pubsubPeerDiscovery()
discovery process. Should I forkjs-libp2p-relay-server
to upgrade libs ? Or do I use a bad setup ? Or is it a bug ?Thanks