Getting error connecting to tracker

[tanayseven]

If I try to use bugout for either my own project or use one of the demos from the README provided, I get the following error in the browser console:

WebSocket connection to 'wss://hub.bugout.link/' failed: Error in connection establishment: net::ERR_CONNECTION_RESET
WebSocket connection to 'wss://tracker.btorrent.xyz/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID
WebSocket connection to 'wss://hub.bugout.link/' failed: Connection closed before receiving a handshake response

This was not happening before, and just saw this today when I got back to a project that I was working on
The connection between two peers which was working before is not working anymore
I tried on both Firefox as well as Chrome, the result is no different
Also, I'm not running any ad-blocker or site-blocker
I also tried it on two different networks, the problem persists

[chr15m]

@tanayseven it appears the bugout webtorrent tracker server is overloaded. This is a problem with centralized tracker servers. It will take me a while to fix this. Does tracker.openwebtorrent.com still work for you?

[chr15m]

See also #42.

[tanayseven]

How practical is it to use DHT instead of a tracker?

[chr15m]

You can only use the DHT outside the browser. It works in nodejs.

[tanayseven]

Ouch!

[chr15m]

@tanayseven if you want a temporary solution, spin up your own bittorrent-tracker instance and pass that to Bugout.

[tanayseven]

That's what I was supposed to ask you. Can we pass any torrent trackers to Bugout?

[chr15m]

Yes for sure, you can use your own signaling server(s): https://github.com/chr15m/bugout/blob/master/docs/API.md#using-your-own-signaling-servers

[tanayseven]

Cool, thanks! Should I leave this issue open till you fix it?

[phyreman]

It seems only trying to use another tracker like wss://tracker.openwebtorrent.com doesn't create a complete connection, but doesn't give any errors. But if I use on wss://hub.bugout.link, it'll create a connection between users and allow communication. Otherwise, it'll never complete the connection and no other users will enter the room. Since these seem to be the only running WebTorrent trackers, it's no wonder they're being hammered.

[draeder]

@phyreman I built a simple WebTorrent tracker server that can be deployed to Heroku with 1 click that you could use for your projects. You can also clone the repo and run it locally or anywhere else.

https://github.com/draeder/p2p-tracker

[hhff]

Hi @draeder - thank you for this! I just deployed the heroku server - but when I use it in the announce option (as per the docs here), it never finds any peers. Is there something I'm missing?

[tanayseven]

Same here, it never finds any peers when using any of the trackers.