starred/qBittorrent

Fork 0

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

DHT not working in windows 7 for last few days... #3617

New issue

Closed

opened 2026-02-21 16:52:22 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-21 16:52:22 -05:00

Owner

Originally created by @monstervadge on GitHub (Dec 21, 2015).

HI, I have been having trouble with the DHT not getting any nodes after startup. I have been using qbittorrent for about 4 or 5 months without issues. There were only a couple of instances of DHT not working on startup, but it would get nodes after a couple of minutes. Now, for the last few days I have been leaving qbittorrent open all day with nothing happening. Nothing after restarts. I did some searching on here to see if anybody else had any issues similar to mine, but I wasn't able to find what i was looking for. Does anybody else have this problem?

Originally created by @monstervadge on GitHub (Dec 21, 2015). HI, I have been having trouble with the DHT not getting any nodes after startup. I have been using qbittorrent for about 4 or 5 months without issues. There were only a couple of instances of DHT not working on startup, but it would get nodes after a couple of minutes. Now, for the last few days I have been leaving qbittorrent open all day with nothing happening. Nothing after restarts. I did some searching on here to see if anybody else had any issues similar to mine, but I wasn't able to find what i was looking for. Does anybody else have this problem?

deekerman closed this issue

2026-02-21 16:52:25 -05:00

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@chrishirst commented on GitHub (Dec 21, 2015):

And are we supposed to guess if you ARE using qbittorrent or not????????????????

@chrishirst commented on GitHub (Dec 21, 2015): And are we supposed to guess if you ARE using qbittorrent or not????????????????

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@monstervadge commented on GitHub (Dec 21, 2015):

I do apologize, but i was under the impression I was in a qbittorrent thread given that it says so at the top of the page. To answer your question, yes, I'm using qbittorrent v3.3.1 i was using the previous release which was also having the same issue.

@monstervadge commented on GitHub (Dec 21, 2015): I do apologize, but i was under the impression I was in a qbittorrent thread given that it says so at the top of the page. To answer your question, yes, I'm using qbittorrent v3.3.1 i was using the previous release which was also having the same issue.

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@chrishirst commented on GitHub (Dec 22, 2015):

I was in a qbittorrent thread given that it says so at the top of the page

It is but as THIS is for reporting 'bugs' ... WHAT version of qbittorrent you ARE using and reporting IS a VITAL piece of information.

@chrishirst commented on GitHub (Dec 22, 2015): > I was in a qbittorrent thread given that it says so at the top of the page It is but as THIS is for reporting 'bugs' ... WHAT version of qbittorrent you ARE using and reporting **IS a VITAL** piece of information.

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@chrishirst commented on GitHub (Dec 22, 2015):

It is for qbittorrent but is the 'bug' reporting and tracking, so knowing the client version is an vital piece of information, furthermore this is not a confirmed 'bug' report it is more likely just a problem in your settings or your network.

https://github.com/qbittorrent/qBittorrent/wiki/Things-we-need-to-know-to-help-you-with-'speed'-issues

@chrishirst commented on GitHub (Dec 22, 2015): It is for qbittorrent but is the 'bug' reporting and tracking, so knowing the client version is an **vital** piece of information, furthermore this is not a [confirmed 'bug' report](https://github.com/qbittorrent/qBittorrent/wiki/What-is-a-'bug') it is more likely just a problem in your settings or your network. https://github.com/qbittorrent/qBittorrent/wiki/Things-we-need-to-know-to-help-you-with-'speed'-issues

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@Bobb-E-Burns commented on GitHub (Dec 22, 2015):

This is the main reason I switched back from 3.3 to 3.2 though.
I've seen multiple reports here about people not getting any DHT nodes with the new update.
3.2.5 is perfectly fine. So I don't think it has anything to do with

a problem in your settings or your network.

I've tried everything I could think of trying to fix this in 3.3, but nothing helped so I went back to 3.2.

@Bobb-E-Burns commented on GitHub (Dec 22, 2015): This is the main reason I switched back from 3.3 to 3.2 though. I've seen multiple reports here about people not getting any DHT nodes with the new update. 3.2.5 is perfectly fine. So I don't think it has anything to do with > a problem in your settings or your network. I've tried everything I could think of trying to fix this in 3.3, but nothing helped so I went back to 3.2.

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Dec 22, 2015):

@monstervadge can you copy your log here? (delete torrent names/hashes). View->Log

@sledgehammer999 commented on GitHub (Dec 22, 2015): @monstervadge can you copy your log here? (delete torrent names/hashes). `View->Log`

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@Bobb-E-Burns commented on GitHub (Dec 23, 2015):

@sledgehammer999 This was mine
qBittorrent failed listening on interface ***** Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.

@Bobb-E-Burns commented on GitHub (Dec 23, 2015): @sledgehammer999 This was mine `qBittorrent failed listening on interface ***** Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.`

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Dec 23, 2015):

@Nhoise is that the correct interface you have commented out? (there isn't a harm if you let us see it). If yes, try changing your port to something else and see if that helps.

@sledgehammer999 commented on GitHub (Dec 23, 2015): @Nhoise is that the correct interface you have commented out? (there isn't a harm if you let us see it). If yes, try changing your port to something else and see if that helps.

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@Bobb-E-Burns commented on GitHub (Dec 23, 2015):

It showed different things depending on what kind of interface selected in the options. Something like 00.0.0.:: for any interface, 192.168 for my wireless etc. That's why I replaced it with *'s.

I've since downgraded to 3.2.5 so I can't further troubleshoot 3.3.
But shouldn't using the same port between 3.2.5 and 3.3 give no problems, basically everything is still the same config wise.
Specified ports are open, firewall is not blocking anything for qbit.
Just that message popping up in the log (most of the time) when starting 3.3.
Got it to work a couple times though, after being persistent with restarts. But the last time I tried I couldn't get it to work, I probably gave it 15+ restarts, so I gave up and just went back to 3.2.5

@Bobb-E-Burns commented on GitHub (Dec 23, 2015): It showed different things depending on what kind of interface selected in the options. Something like `00.0.0.::` for any interface, `192.168` for my wireless etc. That's why I replaced it with *'s. I've since downgraded to 3.2.5 so I can't further troubleshoot 3.3. But shouldn't using the same port between 3.2.5 and 3.3 give no problems, basically everything is still the same config wise. Specified ports are open, firewall is not blocking anything for qbit. Just that message popping up in the log (most of the time) when starting 3.3. Got it to work a couple times though, after being persistent with restarts. But the last time I tried I couldn't get it to work, I probably gave it 15+ restarts, so I gave up and just went back to 3.2.5

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@markxander commented on GitHub (Dec 25, 2015):

I have the same issue. At every startup DHT doesnt work until I manually change the port.

12/25/2015 2:05 PM - qBittorrent is trying to listen on interface 192.168.178.13 port: 20045
12/25/2015 2:05 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: UDP/20045
12/25/2015 2:05 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20045
12/25/2015 2:05 PM - Options were saved successfully.
12/25/2015 2:05 PM - Embedded Tracker [OFF]
12/25/2015 2:05 PM - Encryption support [ON]
12/25/2015 2:05 PM - Local Peer Discovery support [ON]
12/25/2015 2:05 PM - PeX support [ON]
12/25/2015 2:05 PM - Anonymous mode [OFF]
12/25/2015 2:05 PM - HTTP User-Agent is 'qBittorrent v3.3.1'

12/25/2015 2:03 PM - External IP: xx.xx.xx.xx
12/25/2015 2:03 PM - qBittorrent failed listening on interface 192.168.178.13 port: UDP/20046. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.
12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20046
12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: UDP/20046
12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP_SSL/4433
12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20046
12/25/2015 2:03 PM - Options were saved successfully.
12/25/2015 2:03 PM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Dec 2 00:28:22 2015.
12/25/2015 2:03 PM - Embedded Tracker [OFF]
12/25/2015 2:03 PM - Encryption support [ON]
12/25/2015 2:03 PM - Local Peer Discovery support [ON]
12/25/2015 2:03 PM - PeX support [ON]
12/25/2015 2:03 PM - DHT support [ON]
12/25/2015 2:03 PM - Anonymous mode [OFF]
12/25/2015 2:03 PM - HTTP User-Agent is 'qBittorrent v3.3.1'
12/25/2015 2:03 PM - Peer ID: -xxxxxx-
12/25/2015 2:03 PM - qBittorrent is trying to listen on interface 192.168.178.13 port: 20046
12/25/2015 2:03 PM - qBittorrent v3.3.1 started

@markxander commented on GitHub (Dec 25, 2015): I have the same issue. At every startup DHT doesnt work until I manually change the port. 12/25/2015 2:05 PM - qBittorrent is trying to listen on interface 192.168.178.13 port: 20045 12/25/2015 2:05 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: UDP/20045 12/25/2015 2:05 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20045 12/25/2015 2:05 PM - Options were saved successfully. 12/25/2015 2:05 PM - Embedded Tracker [OFF] 12/25/2015 2:05 PM - Encryption support [ON] 12/25/2015 2:05 PM - Local Peer Discovery support [ON] 12/25/2015 2:05 PM - PeX support [ON] 12/25/2015 2:05 PM - Anonymous mode [OFF] 12/25/2015 2:05 PM - HTTP User-Agent is 'qBittorrent v3.3.1' 12/25/2015 2:03 PM - External IP: xx.xx.xx.xx 12/25/2015 2:03 PM - qBittorrent failed listening on interface 192.168.178.13 port: UDP/20046. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted. 12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20046 12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: UDP/20046 12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP_SSL/4433 12/25/2015 2:03 PM - qBittorrent is successfully listening on interface 192.168.178.13 port: TCP/20046 12/25/2015 2:03 PM - Options were saved successfully. 12/25/2015 2:03 PM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Dec 2 00:28:22 2015. 12/25/2015 2:03 PM - Embedded Tracker [OFF] 12/25/2015 2:03 PM - Encryption support [ON] 12/25/2015 2:03 PM - Local Peer Discovery support [ON] 12/25/2015 2:03 PM - PeX support [ON] 12/25/2015 2:03 PM - DHT support [ON] 12/25/2015 2:03 PM - Anonymous mode [OFF] 12/25/2015 2:03 PM - HTTP User-Agent is 'qBittorrent v3.3.1' 12/25/2015 2:03 PM - Peer ID: -xxxxxx- 12/25/2015 2:03 PM - qBittorrent is trying to listen on interface 192.168.178.13 port: 20046 12/25/2015 2:03 PM - qBittorrent v3.3.1 started

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@monstervadge commented on GitHub (Dec 26, 2015):

Here's the most recent log. my connection status is online, but DHT has worked only once in the last few days since I first posted the question.

12/26/2015 10:27 AM - External IP: xxx.xxx.xxx.xxx
12/26/2015 10:27 AM - qBittorrent failed listening on interface 0.0.0.0 port: UDP/18309. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP/18309
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/18309
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/18309
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP/18309
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/18309
12/26/2015 10:27 AM - Options were saved successfully.
12/26/2015 10:27 AM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Dec 1 15:28:22 2015.
12/26/2015 10:27 AM - UPnP / NAT-PMP support [ON]
12/26/2015 10:27 AM - Embedded Tracker [OFF]
12/26/2015 10:27 AM - Encryption support [FORCED]
12/26/2015 10:27 AM - Local Peer Discovery support [ON]
12/26/2015 10:27 AM - PeX support [ON]
12/26/2015 10:27 AM - DHT support [ON]
12/26/2015 10:27 AM - Anonymous mode [OFF]
12/26/2015 10:27 AM - HTTP User-Agent is 'qBittorrent v3.3.1'
12/26/2015 10:27 AM - Peer ID: -xxxxxx-
12/26/2015 10:27 AM - qBittorrent is trying to listen on any interface port: 18309
12/26/2015 10:27 AM - qBittorrent v3.3.1 started

@monstervadge commented on GitHub (Dec 26, 2015): Here's the most recent log. my connection status is online, but DHT has worked only once in the last few days since I first posted the question. 12/26/2015 10:27 AM - External IP: xxx.xxx.xxx.xxx 12/26/2015 10:27 AM - qBittorrent failed listening on interface 0.0.0.0 port: UDP/18309. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted. 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP/18309 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/18309 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/18309 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface :: port: TCP/18309 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433 12/26/2015 10:27 AM - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/18309 12/26/2015 10:27 AM - Options were saved successfully. 12/26/2015 10:27 AM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Dec 1 15:28:22 2015. 12/26/2015 10:27 AM - UPnP / NAT-PMP support [ON] 12/26/2015 10:27 AM - Embedded Tracker [OFF] 12/26/2015 10:27 AM - Encryption support [FORCED] 12/26/2015 10:27 AM - Local Peer Discovery support [ON] 12/26/2015 10:27 AM - PeX support [ON] 12/26/2015 10:27 AM - DHT support [ON] 12/26/2015 10:27 AM - Anonymous mode [OFF] 12/26/2015 10:27 AM - HTTP User-Agent is 'qBittorrent v3.3.1' 12/26/2015 10:27 AM - Peer ID: -xxxxxx- 12/26/2015 10:27 AM - qBittorrent is trying to listen on any interface port: 18309 12/26/2015 10:27 AM - qBittorrent v3.3.1 started

deekerman commented

2026-02-21 16:52:26 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 20, 2018):

Old issue, possibly fixed by now. Make a new one if it persists.

@thalieht commented on GitHub (Sep 20, 2018): Old issue, possibly fixed by now. Make a new one if it persists.

deekerman referenced this issue

2026-02-21 18:38:21 -05:00

FIX Some Dialogs positioned wrong in HiDPI with scaling #6832