3.3 all new torrents stalled #3397

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

The subfolders are not being created for the new torrents. I try Open Destination Folder and nothing happens. I can even attempt to download the same torrent again, and it doesn't ask to update trackers. In fact, the tracker field is blank on all my torrents. Wacko!

@cpscooter commented on GitHub (Nov 30, 2015): The subfolders are not being created for the new torrents. I try Open Destination Folder and nothing happens. I can even attempt to download the same torrent again, and it doesn't ask to update trackers. In fact, the tracker field is blank on all my torrents. Wacko!

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

All the new torrents say there are 0 seeds and peers in QBT, but they have many according to the web site.

@cpscooter commented on GitHub (Nov 30, 2015): All the new torrents say there are 0 seeds and peers in QBT, but they have many according to the web site.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

I just tried another torrent, but this time I set the destination on a local disk instead of the NAS. The status is Queued (instead of stalled). Yet the Seeds and Peers are still 0, and it is not downloading.
Should I attempt a downgrade in spite of the warning to not attempt it?

@cpscooter commented on GitHub (Nov 30, 2015): I just tried another torrent, but this time I set the destination on a local disk instead of the NAS. The status is Queued (instead of stalled). Yet the Seeds and Peers are still 0, and it is not downloading. Should I attempt a downgrade in spite of the warning to not attempt it?

deekerman commented

Author

Owner

@deadaluspark commented on GitHub (Nov 30, 2015):

I am having this same issue. All new torrents just sit at stalled. Tried using solutions from previous times this same issue happened during upgrade, nothing is helping.

I'm with you cpscooter, I wish I hadn't bothered to upgrade. This is a huge pain in the ass.

@deadaluspark commented on GitHub (Nov 30, 2015): I am having this same issue. All new torrents just sit at stalled. Tried using solutions from previous times this same issue happened during upgrade, nothing is helping. I'm with you cpscooter, I wish I hadn't bothered to upgrade. This is a huge pain in the ass.

deekerman commented

Author

Owner

@jpsona commented on GitHub (Nov 30, 2015):

Same issue here since upgrading to 3.3.0. All torrents stalled. Connection status: no direct connections; DHT: 0 nodes, if it helps.

@jpsona commented on GitHub (Nov 30, 2015): Same issue here since upgrading to 3.3.0. All torrents stalled. Connection status: no direct connections; DHT: 0 nodes, if it helps.

deekerman commented

Author

Owner

@sledgehammer999 commented on GitHub (Nov 30, 2015):

Restart qbt and copy your log here(omit torrent hashes and names).
View->Log

@sledgehammer999 commented on GitHub (Nov 30, 2015): Restart qbt and copy your log here(omit torrent hashes and names). View->Log

deekerman commented

Author

Owner

@deadaluspark commented on GitHub (Nov 30, 2015):

11/29/2015 11:12 PM - Couldn't download favicon for URL 'http://publicbt.com/favicon.ico'. Reason: The remote host name was not found (invalid hostname)
11/29/2015 11:12 PM - Couldn't decode favicon for URL 'http://glotorrents.pw/favicon.png'.
11/29/2015 11:12 PM - Couldn't decode favicon for URL 'http://glotorrents.pw/favicon.ico'. Trying to download favicon in PNG format.
11/29/2015 11:12 PM - Couldn't download favicon for URL 'http://publicbt.com/favicon.png'. Reason: The remote host name was not found (invalid hostname)
11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: UDP/8999
11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP/8999
11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: UDP/8999
11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP_SSL/4433
11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP/8999
11/29/2015 11:12 PM - Options were saved successfully.
11/29/2015 11:12 PM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Nov 3 15:05:56 2015.
11/29/2015 11:12 PM - UPnP / NAT-PMP support [ON]
11/29/2015 11:12 PM - Embedded Tracker [OFF]
11/29/2015 11:12 PM - Encryption support [ON]
11/29/2015 11:12 PM - Local Peer Discovery support [ON]
11/29/2015 11:12 PM - PeX support [ON]
11/29/2015 11:12 PM - DHT support [ON]
11/29/2015 11:12 PM - Anonymous mode [OFF]
11/29/2015 11:12 PM - HTTP User-Agent is 'qBittorrent v3.3.0'
11/29/2015 11:12 PM - Peer ID: -qB3300-
11/29/2015 11:12 PM - qBittorrent is trying to listen on interface 127.0.0.1 port: 8999
11/29/2015 11:12 PM - The network interface defined is invalid: {53C0BC8E-0EFA-4AF2-8B80-B228EC86C8B3}
11/29/2015 11:12 PM - qBittorrent v3.3.0 started

@deadaluspark commented on GitHub (Nov 30, 2015): 11/29/2015 11:12 PM - Couldn't download favicon for URL 'http://publicbt.com/favicon.ico'. Reason: The remote host name was not found (invalid hostname) 11/29/2015 11:12 PM - Couldn't decode favicon for URL 'http://glotorrents.pw/favicon.png'. 11/29/2015 11:12 PM - Couldn't decode favicon for URL 'http://glotorrents.pw/favicon.ico'. Trying to download favicon in PNG format. 11/29/2015 11:12 PM - Couldn't download favicon for URL 'http://publicbt.com/favicon.png'. Reason: The remote host name was not found (invalid hostname) 11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: UDP/8999 11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP/8999 11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: UDP/8999 11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP_SSL/4433 11/29/2015 11:12 PM - qBittorrent is successfully listening on interface 127.0.0.1 port: TCP/8999 11/29/2015 11:12 PM - Options were saved successfully. 11/29/2015 11:12 PM - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Nov 3 15:05:56 2015. 11/29/2015 11:12 PM - UPnP / NAT-PMP support [ON] 11/29/2015 11:12 PM - Embedded Tracker [OFF] 11/29/2015 11:12 PM - Encryption support [ON] 11/29/2015 11:12 PM - Local Peer Discovery support [ON] 11/29/2015 11:12 PM - PeX support [ON] 11/29/2015 11:12 PM - DHT support [ON] 11/29/2015 11:12 PM - Anonymous mode [OFF] 11/29/2015 11:12 PM - HTTP User-Agent is 'qBittorrent v3.3.0' 11/29/2015 11:12 PM - Peer ID: -qB3300- 11/29/2015 11:12 PM - qBittorrent is trying to listen on interface 127.0.0.1 port: 8999 11/29/2015 11:12 PM - The network interface defined is invalid: {53C0BC8E-0EFA-4AF2-8B80-B228EC86C8B3} 11/29/2015 11:12 PM - qBittorrent v3.3.0 started

deekerman commented

Author

Owner

@sledgehammer999 commented on GitHub (Nov 30, 2015):

11/29/2015 11:12 PM - The network interface defined is invalid: {53C0BC8E-0EFA-4AF2-8B80-B228EC86C8B3}

There's your problem. Go to your advanced settings and choose your network interface again. You might need to restart qbt after that.

@sledgehammer999 commented on GitHub (Nov 30, 2015): > 11/29/2015 11:12 PM - The network interface defined is invalid: {53C0BC8E-0EFA-4AF2-8B80-B228EC86C8B3} There's your problem. Go to your advanced settings and choose your network interface again. You might need to restart qbt after that.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

@cpscooter commented on GitHub (Nov 30, 2015): ![qbt log](https://cloud.githubusercontent.com/assets/13418914/11472427/5424a902-9721-11e5-8151-337b1cb8cec5.png)

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

My network was set to Any Interface, so I changed it to my LAN. No change on the new torrents, even after restarting.

@cpscooter commented on GitHub (Nov 30, 2015): My network was set to Any Interface, so I changed it to my LAN. No change on the new torrents, even after restarting.

deekerman commented

Author

Owner

@jpsona commented on GitHub (Nov 30, 2015):

For me this fix worked. Mine was set to Ethernet, switched it to Any and after a restart everything was flowing.

Not sure what 3.3 did as everything was working fine beforehand.

@jpsona commented on GitHub (Nov 30, 2015): For me this fix worked. Mine was set to Ethernet, switched it to Any and after a restart everything was flowing. Not sure what 3.3 did as everything was working fine beforehand.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

I notice when I start qbt the tracker column starts filled in, then they all get cleared out except for a few. Could this be related?

@cpscooter commented on GitHub (Nov 30, 2015): I notice when I start qbt the tracker column starts filled in, then they all get cleared out except for a few. Could this be related?

deekerman commented

Author

Owner

@deadaluspark commented on GitHub (Nov 30, 2015):

I had to change it a few times, but it eventually worked when set to "Any." I set it to that originally and restarted qb, but it didn't change anything. I tried a few other options with no luck, eventually trying "Any" again. It started working immediately, didn't even need to restart qb again. Thanks for all the help.

@deadaluspark commented on GitHub (Nov 30, 2015): I had to change it a few times, but it eventually worked when set to "Any." I set it to that originally and restarted qb, but it didn't change anything. I tried a few other options with no luck, eventually trying "Any" again. It started working immediately, didn't even need to restart qb again. Thanks for all the help.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

I have tried the above and still no joy with any of the network connections listed. Could it be something different in Windows 10? Note: there are a couple of extra network connections listed under advanced options in qbt that don't exist. I have only one "Local Area Connection", which is listed...but Local Area Connection* 3 and Local Area Connection* 4 are also listed and don't exist.

@cpscooter commented on GitHub (Nov 30, 2015): I have tried the above and still no joy with any of the network connections listed. Could it be something different in Windows 10? Note: there are a couple of extra network connections listed under advanced options in qbt that don't exist. I have only one "Local Area Connection", which is listed...but Local Area Connection\* 3 and Local Area Connection\* 4 are also listed and don't exist.

deekerman commented

Author

Owner

@deadaluspark commented on GitHub (Nov 30, 2015):

cpscooter, I had the same issue with it not working, and having lots of weird connections listed. I am also in Windows 10.

Like I said, the first time I tried "Any connection" it didn't actually work. Just keep trying different connections and going back to "Any" in between, restarting qb each time you change a setting. It may still not work for you, but in the end it worked for me. Anyway, I don't think it has anything to do with Windows 10 specifically.

@deadaluspark commented on GitHub (Nov 30, 2015): cpscooter, I had the same issue with it not working, and having lots of weird connections listed. I am also in Windows 10. Like I said, the first time I tried "Any connection" it didn't actually work. Just keep trying different connections and going back to "Any" in between, restarting qb each time you change a setting. It may still not work for you, but in the end it worked for me. Anyway, I don't think it has anything to do with Windows 10 specifically.

deekerman commented

Author

Owner

@sledgehammer999 commented on GitHub (Nov 30, 2015):

@cpscooter Choose "Any interface" and uncheck "Listen on IPv6 address". Restart. If it still doesn't connect paste your log here(remove torrent names/hashes). View->Log

@sledgehammer999 commented on GitHub (Nov 30, 2015): @cpscooter Choose "Any interface" and uncheck "Listen on IPv6 address". Restart. If it still doesn't connect paste your log here(remove torrent names/hashes). `View->Log`

deekerman commented

Author

Owner

@Royern commented on GitHub (Nov 30, 2015):

I think i just solved it in my case. Had the same problems as the rest of you. In the connection menu the proxy was set at proxy 4, not by me i think, i changed it to none and voila everything worked. Can someone confirm it was not disabled by default? I can not remember having touched that setting before or after the upgrade.

@Royern commented on GitHub (Nov 30, 2015): I think i just solved it in my case. Had the same problems as the rest of you. In the connection menu the proxy was set at proxy 4, not by me i think, i changed it to none and voila everything worked. Can someone confirm it was not disabled by default? I can not remember having touched that setting before or after the upgrade.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Nov 30, 2015):

Thanks @Royern I looked there and my proxy was not set, but my UPnP was checked. I unchecked uPnP (Options->Connections) and torrents started downloading. I still have one stalled though. I'll keep an eye on that one.

@cpscooter commented on GitHub (Nov 30, 2015): Thanks @Royern I looked there and my proxy was not set, but my UPnP was checked. I unchecked uPnP (Options->Connections) and torrents started downloading. I still have one stalled though. I'll keep an eye on that one.

deekerman commented

Author

Owner

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

I'll keep an eye on that one.

Maybe the tracker of that torrent hasn't whitelisted the new version of qbt.
I think everyone here has solved their problems, so closing.

@sledgehammer999 commented on GitHub (Dec 1, 2015): > I'll keep an eye on that one. Maybe the tracker of that torrent hasn't whitelisted the new version of qbt. I think everyone here has solved their problems, so closing.

deekerman commented

Author

Owner

@cpscooter commented on GitHub (Dec 1, 2015):

@sledgehammer999 thanks for your help with this. I think you are right, I need to wait for whitelisting.
Meanwhile, it is mysterious that people's options may have changed as a result of the upgrade. I hope it's only a coincidence.

@cpscooter commented on GitHub (Dec 1, 2015): @sledgehammer999 thanks for your help with this. I think you are right, I need to wait for whitelisting. Meanwhile, it is mysterious that people's options may have changed as a result of the upgrade. I hope it's only a coincidence.

deekerman commented

Author

Owner

@jameyg03 commented on GitHub (Dec 4, 2015):

I ran into the same issue it was set as one of the tap options. I changed to all and it works now. The only thing I am wondering is if it will go through my VPN I use or will it now bypass that since it is set to all :/

@jameyg03 commented on GitHub (Dec 4, 2015): I ran into the same issue it was set as one of the tap options. I changed to all and it works now. The only thing I am wondering is if it will go through my VPN I use or will it now bypass that since it is set to all :/

deekerman commented

Author

Owner

@NeoCool6 commented on GitHub (Dec 5, 2015):

Hi after upgrade from 3.2.5 to 3.3.0, I have the yellow icon "No Direct connections...". But everything appears to be working. I leave below my execution log and any help would be appreciated (thanks):

05-12-2015 08:57 - External IP: XXX.YYY.ZZZ.NNN
05-12-2015 08:57 - Couldn't download favicon for URL 'http://publicbt.com/favicon.png'. Reason: The remote host name was not found (invalid hostname)
05-12-2015 08:57 - Couldn't download favicon for URL 'http://publicbt.com/favicon.ico'. Reason: The remote host name was not found (invalid hostname)
05-12-2015 08:57 - Couldn't download favicon for URL 'http://openbittorrent.com/favicon.ico'. Reason: The remote content was not found at the server (404)
05-12-2015 08:57 - qBittorrent failed listening on interface 0.0.0.0 port: UDP/55665. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted
05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP/55665
05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/55665
05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/55665
05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP/55665
05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/55665
05-12-2015 08:57 - Options were saved successfully.
05-12-2015 08:57 - The Web UI is listening on port -7871
05-12-2015 08:57 - GeoIP database loaded. Type: GeoLite2-Country. Build time: ter Dez 1 23:28:22 2015.
05-12-2015 08:57 - Embedded Tracker [OFF]
05-12-2015 08:57 - Encryption support [FORCED]
05-12-2015 08:57 - Local Peer Discovery support [OFF]
05-12-2015 08:57 - PeX support [OFF]
05-12-2015 08:57 - Anonymous mode [OFF]
05-12-2015 08:57 - HTTP User-Agent is 'qBittorrent v3.3.0'
05-12-2015 08:57 - Peer ID: -qB3300-
05-12-2015 08:57 - qBittorrent is trying to listen on any interface port: 55665
05-12-2015 08:57 - qBittorrent v3.3.0 started

@NeoCool6 commented on GitHub (Dec 5, 2015): Hi after upgrade from 3.2.5 to 3.3.0, I have the yellow icon "No Direct connections...". But everything appears to be working. I leave below my execution log and any help would be appreciated (thanks): 05-12-2015 08:57 - External IP: XXX.YYY.ZZZ.NNN 05-12-2015 08:57 - Couldn't download favicon for URL 'http://publicbt.com/favicon.png'. Reason: The remote host name was not found (invalid hostname) 05-12-2015 08:57 - Couldn't download favicon for URL 'http://publicbt.com/favicon.ico'. Reason: The remote host name was not found (invalid hostname) 05-12-2015 08:57 - Couldn't download favicon for URL 'http://openbittorrent.com/favicon.ico'. Reason: The remote content was not found at the server (404) 05-12-2015 08:57 - qBittorrent failed listening on interface 0.0.0.0 port: UDP/55665. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted 05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP/55665 05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/55665 05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/55665 05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433 05-12-2015 08:57 - qBittorrent is successfully listening on interface :: port: TCP/55665 05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433 05-12-2015 08:57 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/55665 05-12-2015 08:57 - Options were saved successfully. 05-12-2015 08:57 - The Web UI is listening on port -7871 05-12-2015 08:57 - GeoIP database loaded. Type: GeoLite2-Country. Build time: ter Dez 1 23:28:22 2015. 05-12-2015 08:57 - Embedded Tracker [OFF] 05-12-2015 08:57 - Encryption support [FORCED] 05-12-2015 08:57 - Local Peer Discovery support [OFF] 05-12-2015 08:57 - PeX support [OFF] 05-12-2015 08:57 - Anonymous mode [OFF] 05-12-2015 08:57 - HTTP User-Agent is 'qBittorrent v3.3.0' 05-12-2015 08:57 - Peer ID: -qB3300- 05-12-2015 08:57 - qBittorrent is trying to listen on any interface port: 55665 05-12-2015 08:57 - qBittorrent v3.3.0 started

deekerman commented

Author

Owner

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

13-12-2015 15:31 - qBittorrent failed listening on interface *****
Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.

This keeps happening to me as well.
Often a few restarts fixes it but right now I can't get it to function at all.

@Bobb-E-Burns commented on GitHub (Dec 13, 2015): `13-12-2015 15:31 - qBittorrent failed listening on interface *****` `Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted.` This keeps happening to me as well. Often a few restarts fixes it but right now I can't get it to function at all.

deekerman commented

Author

Owner

@longsoft-dev commented on GitHub (Dec 28, 2015):

Seems a bug in 3.3.1 too. I had to revert to v3.2.5 and worked again.

@longsoft-dev commented on GitHub (Dec 28, 2015): Seems a bug in 3.3.1 too. I had to revert to v3.2.5 and worked again.

deekerman commented

Author

Owner

@robman75 commented on GitHub (Dec 31, 2015):

I'm new to qbit but have installed and I'm suffering from the same "no direct connections" error. I've tried all the above suggestions but I'm still suffering the same issue.

Here's my log if it holds any answers. Thank you.

1/01/2016 11:59 a.m. - 'And Then There Were None S01E01 (26 December 2015).mp4' resumed. (fast resume)
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/33351
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP/33351
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/33351
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/33351
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP/33351
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/33351
1/01/2016 11:59 a.m. - Options were saved successfully.
1/01/2016 11:59 a.m. - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Dec 2 12:28:22 2015.
1/01/2016 11:59 a.m. - UPnP / NAT-PMP support [ON]
1/01/2016 11:59 a.m. - Embedded Tracker [OFF]
1/01/2016 11:59 a.m. - Encryption support [ON]
1/01/2016 11:59 a.m. - Local Peer Discovery support [ON]
1/01/2016 11:59 a.m. - PeX support [ON]
1/01/2016 11:59 a.m. - DHT support [ON]
1/01/2016 11:59 a.m. - Anonymous mode [OFF]
1/01/2016 11:59 a.m. - HTTP User-Agent is 'qBittorrent v3.3.1'
1/01/2016 11:59 a.m. - Peer ID: -qB3310-
1/01/2016 11:59 a.m. - qBittorrent is trying to listen on any interface port: 33351
1/01/2016 11:59 a.m. - qBittorrent v3.3.1 started

@robman75 commented on GitHub (Dec 31, 2015): I'm new to qbit but have installed and I'm suffering from the same "no direct connections" error. I've tried all the above suggestions but I'm still suffering the same issue. Here's my log if it holds any answers. Thank you. 1/01/2016 11:59 a.m. - 'And Then There Were None S01E01 (26 December 2015).mp4' resumed. (fast resume) 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/33351 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP/33351 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/33351 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/33351 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface :: port: TCP/33351 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433 1/01/2016 11:59 a.m. - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/33351 1/01/2016 11:59 a.m. - Options were saved successfully. 1/01/2016 11:59 a.m. - GeoIP database loaded. Type: GeoLite2-Country. Build time: Wed Dec 2 12:28:22 2015. 1/01/2016 11:59 a.m. - UPnP / NAT-PMP support [ON] 1/01/2016 11:59 a.m. - Embedded Tracker [OFF] 1/01/2016 11:59 a.m. - Encryption support [ON] 1/01/2016 11:59 a.m. - Local Peer Discovery support [ON] 1/01/2016 11:59 a.m. - PeX support [ON] 1/01/2016 11:59 a.m. - DHT support [ON] 1/01/2016 11:59 a.m. - Anonymous mode [OFF] 1/01/2016 11:59 a.m. - HTTP User-Agent is 'qBittorrent v3.3.1' 1/01/2016 11:59 a.m. - Peer ID: -qB3310- 1/01/2016 11:59 a.m. - qBittorrent is trying to listen on any interface port: 33351 1/01/2016 11:59 a.m. - qBittorrent v3.3.1 started

deekerman commented

Author

Owner

@Snake883 commented on GitHub (Jan 21, 2016):

Same problem:
"qBittorrent failed listening on interface 0.0.0.0 port: UDP/. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted."

DHT=0

v3.3.3

@Snake883 commented on GitHub (Jan 21, 2016): Same problem: "qBittorrent failed listening on interface 0.0.0.0 port: UDP/<PORT>. Reason: Only one usage of each socket address (protocol/network address/port) is normally permitted." DHT=0 v3.3.3

deekerman commented

Author

Owner

@kaizokan commented on GitHub (Feb 10, 2016):

@sledgehammer999 Thanks!
changed Network Interface in LAN and restarted (after that set back to Any again)

@kaizokan commented on GitHub (Feb 10, 2016): @sledgehammer999 Thanks! changed Network Interface in LAN and restarted (after that set back to Any again)

deekerman commented

Author

Owner

@Snake883 commented on GitHub (Jun 8, 2017):

My problem seems to be related to torrent queuing.

Maximum torrents = 10
Maximum download = 10
Maximum uploads = 3

If I have both uploads and downloads, I should have 7 (10-3) torrents that I can download.
But I don't. My torrent downloads are queued. I have 0 active torrents.
If I force them, they will download (and yes they have plenty of seeds).
If I disable torrent queuing, they will download.

@Snake883 commented on GitHub (Jun 8, 2017): My problem seems to be related to torrent queuing. Maximum torrents = 10 Maximum download = 10 Maximum uploads = 3 If I have both uploads and downloads, I should have 7 (10-3) torrents that I can download. But I don't. My torrent downloads are queued. I have 0 active torrents. If I force them, they will download (and yes they have plenty of seeds). If I disable torrent queuing, they will download. ![image](https://user-images.githubusercontent.com/8312560/26940699-8a40bbbe-4c30-11e7-9147-98c02eedb162.png) ![image](https://user-images.githubusercontent.com/8312560/26940707-915c41ca-4c30-11e7-88bc-59b0dd41a4d1.png)

deekerman commented

Author

Owner

@Snake883 commented on GitHub (Jun 8, 2017):

Something is definitely going wrong with Torrent Queuing; and maybe something with the "Do not count slow torrents in these links" with no check mark.

If I check mark the "do not count slow torrents", torrents works.

@Snake883 commented on GitHub (Jun 8, 2017): Something is definitely going wrong with Torrent Queuing; and maybe something with the "Do not count slow torrents in these links" with no check mark. If I check mark the "do not count slow torrents", torrents works.

deekerman commented