You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: Timeout: torrent took too long to load at TorrentManager.loadTorrent (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:204:34) at async TorrentManager.loadFromInfoHash (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:137:21) at async TorrentManager.resolveTorrent (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:104:23) at async C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\index.js:84:27 at async fetch (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\make-fetch\index.js:37:9) at async AsyncFunction.protocolHandler (file:///C:/Users/hey/AppData/Local/Programs/agregore-browser/resources/app.asar.unpacked/app/protocols/fetch-to-handler.js:75:24)
Infohash that works properly in the qBittorrent torrent client
The text was updated successfully, but these errors were encountered:
i've had this issue multiple times and played around with it a lot. the best way to have torrents work is make sure the torrents are well seeded. i have tried webtorrent with only 1 test seeder(one of my other pc), and it times out most of the time. but when i have 2 or more seeders, especially a server that is not behind NAT, then it never times out.
how well seeded is this torrent? i am trying to download this torrent on qbittorrent and it is not finding the torrent.
i've had this issue multiple times and played around with it a lot. the best way to have torrents work is make sure the torrents are well seeded. i have tried webtorrent with only 1 test seeder(one of my other pc), and it times out most of the time. but when i have 2 or more seeders, especially a server that is not behind NAT, then it never times out.
how well seeded is this torrent? i am trying to download this torrent on qbittorrent and it is not finding the torrent.
torrent by YTS I have downloaded it on qbittorrent
agregore-browser versions: 2.3.0
OS: Windows 10
issues
There's been an error with the magnet link.
magnet:?xt=urn:btih:8DE461318B965DEA859CFD1805829105770AA13D&dn=Journey+to+the+West+%282013%29+%5B1080p%5D+%5BYTS.MX%5D&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Fopen.tracker.cl%3A1337%2Fannounce&tr=udp%3A%2F%2Fp4p.arenabg.com%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftracker.dler.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fopen.stealth.si%3A80%2Fannounce&tr=udp%3A%2F%2Fipv4.tracker.harry.lu%3A80%2Fannounce&tr=https%3A%2F%2Fopentracker.i2p.rocks%3A443%2Fannounce
Error message
Magnet has no bittorrent infohash
Error
Error: Timeout: torrent took too long to load at TorrentManager.loadTorrent (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:204:34) at async TorrentManager.loadFromInfoHash (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:137:21) at async TorrentManager.resolveTorrent (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\torrent-manager.js:104:23) at async C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\bt-fetch\index.js:84:27 at async fetch (C:\Users\hey\AppData\Local\Programs\agregore-browser\resources\app.asar.unpacked\node_modules\make-fetch\index.js:37:9) at async AsyncFunction.protocolHandler (file:///C:/Users/hey/AppData/Local/Programs/agregore-browser/resources/app.asar.unpacked/app/protocols/fetch-to-handler.js:75:24)
Infohash that works properly in the qBittorrent torrent client
The text was updated successfully, but these errors were encountered: