search

libp2p / js-libp2p-webrtc-star

libp2p WebRTC transport that includes a discovery mechanism provided by the signalling-star
https://libp2p.io
Other
320 stars 96 forks source link

Error: Transport (WebRTCStar) could not listen on any available address #403

Closed ratik21 closed 2 years ago

ratik21 commented 2 years ago

Following up after this issue, i tried to follow this comment to setup a local signalling server :: https://github.com/libp2p/js-libp2p-webrtc-star/issues/238#issue-651546634. So using nginx + certbox to generate certs, and then using docker-compose file, i was able to deploy the server locally.

Terminal log: image

Browser: image

So now i wanted to use it in an example (say peer discovery using webrtc-star transport). But i get the following error:

Error: Transport (WebRTCStar) could not listen on any available address
    at TransportManager.listen (/home/ratik/Zero/zChain/packages/zchain-core/node_modules/libp2p/src/transport-manager.js:201:23)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

image

NOTE: Using the public webrtc-star server works -- wrtc-star1.par.dwebops.pub, wrtc-star2.sjc.dwebops.pub.

cc: @jjperezaguinaga

ratik21 commented 2 years ago

Interestingly :: when i deploy using the heroku setup mentioned here, the server get's deployed, and the peer discovery works as well. But the local server mentioned above doesn't work. Trying to understand what's happening here :/

mateuszjarzewski commented 2 years ago

Interestingly :: when i deploy using the heroku setup mentioned here, the server get's deployed, and the peer discovery works as well. But the local server mentioned above doesn't work. Trying to understand what's happening here :/

I does not, it crashes while handling very first request.

achingbrain commented 2 years ago

@mateuszjarzewski there was a bug that caused a crash with the first request - it was fixed a week ago, could you please try again with the latest version?

BigLep commented 2 years ago

@mateuszjarzewski : we're going to resolve since we believe we have fixed the issue per the comment above. Feel free to reopen if that's not the case.