It seems that the deployed tracker at wss://tracker.openwebtorrent.com is unreliable since connections are often closed after a few seconds (since it's one of the few public WebTorrent trackers, it's probably overloaded). Therefore, I don't know if the libtorrent client fails to keep the connection alive or if the connection is closed because of an error. What is puzzling me is that it works fine with openwebtorrent-tracker when it is deployed locally.
Is the current running code the same as the current master branch?
There might be a compatibility issue with the WebTorrent implementation in libtorrent: https://github.com/arvidn/libtorrent/issues/5831
It seems that the deployed tracker at
wss://tracker.openwebtorrent.comis unreliable since connections are often closed after a few seconds (since it's one of the few public WebTorrent trackers, it's probably overloaded). Therefore, I don't know if the libtorrent client fails to keep the connection alive or if the connection is closed because of an error. What is puzzling me is that it works fine with openwebtorrent-tracker when it is deployed locally.Is the current running code the same as the current master branch?