magnets stuck on metadata until port change. #3989

New issue

Closed

opened 2026-02-21 17:04:24 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 17:04:24 -05:00

Owner

Originally created by @Lestat87 on GitHub (Feb 28, 2016).

Haven't used magnets for a while so assumed it was just something I installed until a friend contacted me to fix his torrents not working issue which turned out to be the same issue. I locked his pc down when I did the OS install so he can't screw it up. Neither of us are running proxies. So we both have installed latest flash, java, win 7 updates, karpersky internet security 16 (mines disabled but drivers still installed). We (coincidentally) had both increased our private tracker seeds from around 120 to 150. I did adjust some of the default qbt settings for both of us. We both have the following active: upnp, DHT, peer exchange, local peer discovery, prefer encryption, geoIP, always announce to all trackers. Firewalls & routers are properly setup. We both have different ISPs though they both lease access from the same network infrastructure owner. Cant be a specific port as switching ports worked then stopped unless they are trialing which ports they can get away with blocking. Didn't see anything useful in the log

When it occurred a pc restart didn't fix. Magnet would get added & stuck indefinitely (8+hrs) on retrieving metadata. I was able to add the .torrent successfully & then add the magnet for torrent found merging trackers message. I didn't check if it actually added the magnet trackers at the time.
I found a solution for another client which had the same issue suggesting change the port used. When I clicked random, changed listening port then applied the magnets started working instantly without a qbt restart. To my surprise it also got a couple of stalled .torrents working again. Each time it has happened changing ports has been successful except in 1 case where it ran qbt using a downloaded magnet link. For that one I had to delete, restart qbt, readding the magnet then change ports.

Could it be a libtorrent bug as I encountered people with similar issue using transmission, vuze & an earlier version of qbt? (cant find the link that had the port switch fix). Or is it likely in all cases we have encountered isp or bandwidth issues?

Edit: forgot mention TCPview showed the port as listening.

Originally created by @Lestat87 on GitHub (Feb 28, 2016). Haven't used magnets for a while so assumed it was just something I installed until a friend contacted me to fix his torrents not working issue which turned out to be the same issue. I locked his pc down when I did the OS install so he can't screw it up. Neither of us are running proxies. So we both have installed latest flash, java, win 7 updates, karpersky internet security 16 (mines disabled but drivers still installed). We (coincidentally) had both increased our private tracker seeds from around 120 to 150. I did adjust some of the default qbt settings for both of us. We both have the following active: upnp, DHT, peer exchange, local peer discovery, prefer encryption, geoIP, always announce to all trackers. Firewalls & routers are properly setup. We both have different ISPs though they both lease access from the same network infrastructure owner. Cant be a specific port as switching ports worked then stopped unless they are trialing which ports they can get away with blocking. Didn't see anything useful in the log When it occurred a pc restart didn't fix. Magnet would get added & stuck indefinitely (8+hrs) on retrieving metadata. I was able to add the .torrent successfully & then add the magnet for torrent found merging trackers message. I didn't check if it actually added the magnet trackers at the time. I found a solution for another client which had the same issue suggesting change the port used. When I clicked random, changed listening port then applied the magnets started working instantly without a qbt restart. To my surprise it also got a couple of stalled .torrents working again. Each time it has happened changing ports has been successful except in 1 case where it ran qbt using a downloaded magnet link. For that one I had to delete, restart qbt, readding the magnet then change ports. Could it be a libtorrent bug as I encountered people with similar issue using transmission, vuze & an earlier version of qbt? (cant find the link that had the port switch fix). Or is it likely in all cases we have encountered isp or bandwidth issues? Edit: forgot mention TCPview showed the port as listening.