Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting error connecting to tracker

See original GitHub issue

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://' failed: Error in connection establishment: net::ERR_CONNECTION_RESET
WebSocket connection to 'wss://' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID
WebSocket connection to 'wss://' 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

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:34 (11 by maintainers)

github_iconTop GitHub Comments

draedercommented, Mar 26, 2021

@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.

draedercommented, Feb 11, 2022

@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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Transmission cannot connect to tracker
Re: Transmission cannot connect to tracker · 1) put some torrent running · 2) change port in preferences · 3) quit transmission without...
Read more >
Transmission 3.0 "Could not connect to tracker" and remote ...
There must be a setting in your network, because the message is saying that the tracker cannot be reached, so the outgoing traffic...
Read more >
Transmission error "Could not connect to tracker" - Reddit
I can ping the trackers in Terminal, and I see the tracker is up on the monitoring sites. Port is open and forwarding...
Read more >
All Fitbit's: Stuck on 'Connecting to Tracker'? Finally Fixed!
I show you how to fix any Fitbit watch where you are stuck on, ' Connecting to Tracker ' screen within the Fitbit...
Read more >
Cannot connect to trackers - Sync
Error "No tracker Connection Available" means that Sync cannot connect to the trackers themselves. To troubleshoot: - Check firewall and router rules: ports ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found