Getting error connecting to tracker

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

[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

[draeder]

@hello-smile6 I’ve been thinking about that. One of the ways I’ve considered doing this is with the library called Hyperswarm. Basically, when a peer requests a torrent that the initial server doesn’t have, it will create a hyperswarm instance using that torrent’s infohash as the swarm identifier. Another server with that infohash will already have a hyperswarm instance for that active torrent, then relay its known peers to the requesting peer, and vice versa to the peers the other server has. If there is no active hyperswarm for that infohash, no trackers know about that torrent so the server behaves as a normal tracker server at that point.

I’ve been diving into things like Kademlia, DHT, webtorrent extensions, simple-peer, and I think I’m getting pretty close to being able to build this.