starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Internet Connection Issues while using Qbittorrent #17243

New issue

Closed

opened 2026-02-22 03:44:37 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-22 03:44:37 -05:00

Owner

Originally created by @KyleK87 on GitHub (Oct 19, 2025).

qBittorrent & operating system versions

Qbittorrent: v5.1.2 x64
Operating system: Windows 10 pro 22H2
Build 19045.6456
QT6 LT20

What is the problem?

So something weird started happening while i was still using v5.1.1 and i tried upgrading to fix the issue with no luck. While Qbittorrent is running my internet will become unusable and sites will start giving me the "this site can't be reached page" as if there's no internet. Connection through both ethernet AND wifi seems to be affected. Torrents will continue downloading but internet browser will become unusable. Eventually everything slows to a stop until i close Qbit. Have tried with chrome and edge same effect. Ran the network troubleshooter which came back with "The remote device or resource won't accept the connection". Tried troubleshooting with my internet provider as well but everything seems to be working on their end. Tried flushing the DNS and resetting the network settings through windows as well :/ also affects wifi on other devices on the same network for reference. Have tried uninstalling and reinstalling the program as well as removing all the Torrents in my list and adding new ones one by one. Also just tried unchecking enable DHT as well as selecting TCP under peer connection protocol but still experiencing the issue.

Steps to reproduce

Uninstalled Qbittorrent and removed all settings.
Reinstalled latest version.
Downloaded a few Torrents.

Additional context

Originally created by @KyleK87 on GitHub (Oct 19, 2025). ### qBittorrent & operating system versions Qbittorrent: v5.1.2 x64 Operating system: Windows 10 pro 22H2 Build 19045.6456 QT6 LT20 ### What is the problem? So something weird started happening while i was still using v5.1.1 and i tried upgrading to fix the issue with no luck. While Qbittorrent is running my internet will become unusable and sites will start giving me the "this site can't be reached page" as if there's no internet. Connection through both ethernet AND wifi seems to be affected. Torrents will continue downloading but internet browser will become unusable. Eventually everything slows to a stop until i close Qbit. Have tried with chrome and edge same effect. Ran the network troubleshooter which came back with "The remote device or resource won't accept the connection". Tried troubleshooting with my internet provider as well but everything seems to be working on their end. Tried flushing the DNS and resetting the network settings through windows as well :/ also affects wifi on other devices on the same network for reference. Have tried uninstalling and reinstalling the program as well as removing all the Torrents in my list and adding new ones one by one. Also just tried unchecking enable DHT as well as selecting TCP under peer connection protocol but still experiencing the issue. ### Steps to reproduce 1. Uninstalled Qbittorrent and removed all settings. 2. Reinstalled latest version. 3. Downloaded a few Torrents. ### Additional context ![Image](https://github.com/user-attachments/assets/62f2f592-a86a-4adc-9c85-881dedba9132)

deekerman

2026-02-22 03:44:37 -05:00

closed this issue
added the
Not an issue
label

deekerman commented

2026-02-22 03:44:43 -05:00

Author

Owner

@lucassantillifuck2fa commented on GitHub (Oct 19, 2025):

Looks like a faulty modem/router, not related to qbittorrent whatsoever, specially considering that the issue started before you installed any update. You could try different clients, I suspect they will cause the same issue, but even in the case they work fine, the only thing you can possibly do to troubleshoot the issue is to replace your modem/router. Only if other clients work AND qbt doesn't work after modem replacement, then it's possible to consider a bug.

@lucassantillifuck2fa commented on GitHub (Oct 19, 2025): Looks like a faulty modem/router, not related to qbittorrent whatsoever, specially considering that the issue started before you installed any update. You could try different clients, I suspect they will cause the same issue, but even in the case they work fine, the only thing you can possibly do to troubleshoot the issue is to replace your modem/router. Only if other clients work AND qbt doesn't work after modem replacement, then it's possible to consider a bug.

deekerman commented

2026-02-22 03:44:45 -05:00

Author

Owner

@KyleK87 commented on GitHub (Oct 19, 2025):

Oops forgot to add that I downloaded transmission and couldn't replicate the issue once Qbittorrent was uninstalled. I noticed a few other people experienced a similar pronoun with other versions
https://github.com/qbittorrent/qBittorrent/issues/18713
I will have to try replacing the router although everything looks fine on their end apparently 🤷‍♂️ I'll swap out the modem and report back. Thanks.

@KyleK87 commented on GitHub (Oct 19, 2025): Oops forgot to add that I downloaded transmission and couldn't replicate the issue once Qbittorrent was uninstalled. I noticed a few other people experienced a similar pronoun with other versions [https://github.com/qbittorrent/qBittorrent/issues/18713](url) I will have to try replacing the router although everything looks fine on their end apparently 🤷‍♂️ I'll swap out the modem and report back. Thanks.

deekerman commented

2026-02-22 03:44:45 -05:00

Author

Owner

@qBittUser commented on GitHub (Oct 20, 2025):

Lower down total global peer connection count, disable local network peer searching and in advanced options specify single network interface and IP.

If replacing WiFi modem/router or device network cards doesn't help, then consider using VPN and wired network or try a different DNS and other network providers to be certain what's causing issues.

@qBittUser commented on GitHub (Oct 20, 2025): Lower down total global peer connection count, disable local network peer searching and in advanced options specify single network interface and IP. If replacing WiFi modem/router or device network cards doesn't help, then consider using VPN and wired network or try a different DNS and other network providers to be certain what's causing issues.

deekerman commented

2026-02-22 03:44:45 -05:00

Author

Owner

@KyleK87 commented on GitHub (Oct 21, 2025):

Okay just to update I've received my new modem everything works well until I launch qbit everything stops working until I reset the modem now. Before I was able to at least download Torrents but now the metadata isn't even being received so not sure what's going on :/ I tried lowering global peers as well as specifying network type and IP And I disabled local network network peer searching. I have also tried changing DNS i tried Google and cloudflare. It's strange as I'm hardwired on my pc but have tried wifi as well and same problem. Internet becomes unusable.

@KyleK87 commented on GitHub (Oct 21, 2025): Okay just to update I've received my new modem everything works well until I launch qbit everything stops working until I reset the modem now. Before I was able to at least download Torrents but now the metadata isn't even being received so not sure what's going on :/ I tried lowering global peers as well as specifying network type and IP And I disabled local network network peer searching. I have also tried changing DNS i tried Google and cloudflare. It's strange as I'm hardwired on my pc but have tried wifi as well and same problem. Internet becomes unusable.

deekerman commented

2026-02-22 03:44:45 -05:00

Author

Owner

@qBittUser commented on GitHub (Oct 21, 2025):

I've received my new modem

What exact modem did you have before and now?

You have latest firmware installed on them?

Any other torrenting client works fine with new modem?

You have latest drivers installed on your computer network devices?

metadata isn't even being received

Better to use *. torrent files than magnet links and recheck if it includes working trackers and recheck if qBittorrent has green globe icon in bottom to be certain that connection works.

Maybe magnet link doesn't include trackers, trackers have limits how often they allow reannounce, have weird connection issues or just you tried downloading unpopular torrent, then most likely have to be patient to receive metadata even with other torrenting clients.

also tried changing DNS

CloudFlare has 2 different kind of DNS.

1dot1dot1dot1.cloudflare-dns.com is less known than 1.1.1.1 is. They use different ports and sometimes one works better than the other.

https://1.1.1.1/help/ shows if your CloudFlare DNS is using using only DNS over HTTPS (DoH) or using DNS over TLS (DoT) or if have both.

@qBittUser commented on GitHub (Oct 21, 2025): > I've received my new modem What exact modem did you have before and now? You have latest firmware installed on them? Any other torrenting client works fine with new modem? You have latest drivers installed on your computer network devices? > metadata isn't even being received Better to use *. torrent files than magnet links and recheck if it includes working trackers and recheck if qBittorrent has green globe icon in bottom to be certain that connection works. Maybe magnet link doesn't include trackers, trackers have limits how often they allow reannounce, have weird connection issues or just you tried downloading unpopular torrent, then most likely have to be patient to receive metadata even with other torrenting clients. > also tried changing DNS CloudFlare has 2 different kind of DNS. 1dot1dot1dot1.cloudflare-dns.com is less known than 1.1.1.1 is. They use different ports and sometimes one works better than the other. [https://1.1.1.1/help/](https://1.1.1.1/help/) shows if your CloudFlare DNS is using using only DNS over HTTPS (DoH) or using DNS over TLS (DoT) or if have both.

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@KyleK87 commented on GitHub (Oct 21, 2025):

Actually now I'm experiencing the issue with qbt, transmission AND deluge. This time around no Torrents will get past the receiving metadata phase so I'm guessing its my pc and maybe not the program or router? The modem I'm using is a sagecom f@st3896 SU Cogeco. I will try upgrading the firmware

@KyleK87 commented on GitHub (Oct 21, 2025): Actually now I'm experiencing the issue with qbt, transmission AND deluge. This time around no Torrents will get past the receiving metadata phase so I'm guessing its my pc and maybe not the program or router? The modem I'm using is a sagecom f@st3896 SU Cogeco. I will try upgrading the firmware

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@qBittUser commented on GitHub (Oct 21, 2025):

my pc and maybe not the program or router?

You have to do more tests and provide more info.

If you have other computer and kept previous modem then try using them.

no Torrents will get past the receiving metadata phase.

I suggested to avoid magnet links, be patient and recheck other things. Also exit other software and don't run multiple torrenting clients simultaneously.

now I'm experiencing the issue with ...

Issue getting metadata or issue of opening up torrent client with or without a single torrent transfer is causing internet or modem to stop working?

f@st3896 SU Cogeco

You had exactly the same modem model before that was working fine with Transmission?

@qBittUser commented on GitHub (Oct 21, 2025): > my pc and maybe not the program or router? You have to do more tests and provide more info. If you have other computer and kept previous modem then try using them. > no Torrents will get past the receiving metadata phase. I suggested to avoid magnet links, be patient and recheck other things. Also exit other software and don't run multiple torrenting clients simultaneously. > now I'm experiencing the issue with ... Issue getting metadata or issue of opening up torrent client with or without a single torrent transfer is causing internet or modem to stop working? > f@st3896 SU Cogeco You had exactly the same modem model before that was working fine with Transmission?

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@KyleK87 commented on GitHub (Oct 21, 2025):

Ill run some more tests now and report back. I do have another computer ill
test on soon. No I was only using one at a time just trying to do trial and
error. Metadata was taking a while but it did eventually work. However my
internet becomes unusable even if there's no torrents just as soon as I
open one of the programs. Yes same exact model and yesterday on the old
modem transmission seemed to be working fine but today all 3 programs
reproduce the issue.

On Tue, Oct 21, 2025, 5:16 p.m. qBittUser @.***> wrote:

qBittUser left a comment (qbittorrent/qBittorrent#23399)
https://github.com/qbittorrent/qBittorrent/issues/23399#issuecomment-3429582031

my pc and maybe not the program or router?

You have to do more tests and provide more info.

If you have other computer and kept previous modem then try using them.

no Torrents will get past the receiving metadata phase.

I suggested to avoid magnet links, be patient and recheck other things.
Also exit other software and don't run multiple torrenting clients
simultaneously.

now I'm experiencing the issue with ...

Issue getting metadata or issue of opening up torrent client with or
without a single torrent transfer is causing internet or modem to stop
working?

@.*** SU Cogeco

You had exactly the same modem model before that was working fine with
Transmission?

—
Reply to this email directly, view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/23399#issuecomment-3429582031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUJZWLUNLNILCOWB2NZJHD3Y2PERAVCNFSM6AAAAACJT6Y25CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRZGU4DEMBTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@KyleK87 commented on GitHub (Oct 21, 2025): Ill run some more tests now and report back. I do have another computer ill test on soon. No I was only using one at a time just trying to do trial and error. Metadata was taking a while but it did eventually work. However my internet becomes unusable even if there's no torrents just as soon as I open one of the programs. Yes same exact model and yesterday on the old modem transmission seemed to be working fine but today all 3 programs reproduce the issue. On Tue, Oct 21, 2025, 5:16 p.m. qBittUser ***@***.***> wrote: > *qBittUser* left a comment (qbittorrent/qBittorrent#23399) > <https://github.com/qbittorrent/qBittorrent/issues/23399#issuecomment-3429582031> > > my pc and maybe not the program or router? > > You have to do more tests and provide more info. > > If you have other computer and kept previous modem then try using them. > > no Torrents will get past the receiving metadata phase. > > I suggested to avoid magnet links, be patient and recheck other things. > Also exit other software and don't run multiple torrenting clients > simultaneously. > > now I'm experiencing the issue with ... > > Issue getting metadata or issue of opening up torrent client with or > without a single torrent transfer is causing internet or modem to stop > working? > > ***@***.*** SU Cogeco > > You had exactly the same modem model before that was working fine with > Transmission? > > — > Reply to this email directly, view it on GitHub > <https://github.com/qbittorrent/qBittorrent/issues/23399#issuecomment-3429582031>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAUJZWLUNLNILCOWB2NZJHD3Y2PERAVCNFSM6AAAAACJT6Y25CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRZGU4DEMBTGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@lucassantillifuck2fa commented on GitHub (Oct 21, 2025):

I have a suggestion, if you use a VPN that supports port forwarding, like ProtonVPN, you will delegate all the incoming and outgoing connections to the VPN server. This way, the only connection happening at router level is the VPN itself. This way, allegedly, if the client works without causing interruptions, the problem will be 100% confirmed to be the router or at least ISP-related, not the torrent client, OS or PC.

I advise you to try the VPN suggestion as it is the easiest way to diagnose and confirm the issue. If everything works smoothly via VPN, you will most likely have to switch to a different ISP.

@lucassantillifuck2fa commented on GitHub (Oct 21, 2025): I have a suggestion, if you use a VPN that supports port forwarding, like ProtonVPN, you will delegate all the incoming and outgoing connections to the VPN server. This way, the only connection happening at router level is the VPN itself. This way, allegedly, if the client works without causing interruptions, the problem will be 100% confirmed to be the router or at least ISP-related, not the torrent client, OS or PC. I advise you to try the VPN suggestion as it is the easiest way to diagnose and confirm the issue. If everything works smoothly via VPN, you will most likely have to switch to a different ISP.

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@KyleK87 commented on GitHub (Oct 22, 2025):

I figured it out! You were right it wasn't the program at all. It was actually the modem I was using. They must have had a firmware update that changed something. I got one of their older hitron models today and it's working perfectly. More customizable as well. Thanks everyone for helping me narrow down the problem and find a solution 🙏🏻

@KyleK87 commented on GitHub (Oct 22, 2025): I figured it out! You were right it wasn't the program at all. It was actually the modem I was using. They must have had a firmware update that changed something. I got one of their older hitron models today and it's working perfectly. More customizable as well. Thanks everyone for helping me narrow down the problem and find a solution 🙏🏻

deekerman commented

2026-02-22 03:44:46 -05:00

Author

Owner

@qBittUser commented on GitHub (Oct 22, 2025):

@KyleK87

It was actually the modem I was using.

If no more network issues with different modem, then you should close this issue report.

@qBittUser commented on GitHub (Oct 22, 2025): @KyleK87 > It was actually the modem I was using. If no more network issues with different modem, then you should close this issue report.