qBittorrent official forums

So I have spent the past few days trying to figure this out. A few weeks ago, QB just stopped working. It shows the yellow connection icon every time upon launch, DHT: 0 nodes, and trackers will not work, much less the torrents themselves. I have searched all over the web and tried everything I ran across. I reset all of the router settings manually and then reset to defaults just to rule that out, tried manual port forwarding, uninstalled QB/reinstalled, changed all of the settings many times to test different things and NOTHING is working. It's really starting to piss me off.

Anywho, system info and QB log is below. I would appreciate any suggestions that I have not thought of or already tried.

QB V. 3.3.10 (Tried reverting to prior releases already too).
Win 10 Pro

If I go to canyouseeme.org and test the port, the icon in QB changes from yellow to green but never does allow any tracker, nodes or torrents to connect or update.

QB Log:

(N) 2017-01-25T00:12:36 - qBittorrent v3.3.10 started
(I) 2017-01-25T00:12:36 - qBittorrent is trying to listen on any interface port: 17306
(N) 2017-01-25T00:12:36 - Peer ID: -qB33A0-
(N) 2017-01-25T00:12:36 - HTTP User-Agent is 'qBittorrent v3.3.10'
(I) 2017-01-25T00:12:36 - DHT support [ON]
(I) 2017-01-25T00:12:36 - Local Peer Discovery support [ON]
(I) 2017-01-25T00:12:36 - PeX support [ON]
(I) 2017-01-25T00:12:36 - Anonymous mode [OFF]
(I) 2017-01-25T00:12:36 - Encryption support [ON]
(I) 2017-01-25T00:12:36 - Embedded Tracker [OFF]
(I) 2017-01-25T00:12:36 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Jan 3 20:59:05 2017.
(N) 2017-01-25T00:12:36 - Options were saved successfully.
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/17306
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface :: port: TCP/17306
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/17306
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/17306
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface :: port: TCP/17306
(I) 2017-01-25T00:12:36 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/17306
(N) 2017-01-25T00:12:36 - 'Star Wars' resumed. (fast resume)
(N) 2017-01-25T00:12:36 - 'star wars' resumed. (fast resume)
(N) 2017-01-25T00:12:36 - 'Marvels.Agents.of.S.H.I.E.L.D.S04E09.HDTV.x264-LOL[ettv]' resumed. (fast resume)
(N) 2017-01-25T00:12:37 - 'The Old Farmer's 2017 Almanac - Special Anniversary Edition (2016) (Epub) Gooner' resumed. (fast resume)
(N) 2017-01-25T00:12:37 - 'archlinux-2017.01.01-dual.iso' resumed. (fast resume)
(I) 2017-01-25T00:12:51 - UPnP / NAT-PMP support [ON]
(N) 2017-01-25T00:12:51 - Options were saved successfully.
(I) 2017-01-25T00:12:53 - External IP: 75.104.220.214
(I) 2017-01-25T00:12:53 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 17306
(I) 2017-01-25T00:12:55 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using UPnP. external port: 17306

Check your W10 firewall settings to see if qB traffic is allowed on both TCP/UDP. If not, add the rules or deactivate the W10 firewall if the one in your router is on.
Uncheck the UPnP/NAT-PMP setting, considering the fact you're using a router.
Check to see if the trackers you're using (private or public? - come back with an answer) are still working.

After all these a PC restart would be a good thing to do.

Next time you're posting logs/screenshots delete/mask your IP, torrent's names and any sensitive information - it's in your own interest. 

Public IP and those torrent names I wasn't particularly concerned with. If it were sensitive, I would've blocked it. However, the UPnP/NAT-PMP settings have all been tweaked. It turns out that the issues lies with Exede internet. Yes, I realize they are one of the worst ISP companies and I wish that they would burn sometimes. Their answer was a bunch of bull at Tier 1, then at Tier 2, they pretty much told me that they don't know why it happens from time to time. We did a few things and reset the modem a few times, blah blah blah. It works now. When it happens again, if it happens again, they said to call when the issue arises...So, still no definitive cause for it; might be the dynamic IP assigned with the satellite internet, might not be.

Instead of a Women's March, we should all march for better ISPs and internet infrastructures. That would be a beneficial cause for everyone.

SOLVED (for me) ver 5.1.0 and previous version

close qBittorrent app (including in the services tray near the clock)
open %AppData% and go to Roaming\qBittorrent using file explorer or similar
delete (or move to a sub folder) the following files:
qBittorrent.ini and
qBittorrent-data.ini

then restart qBittorrent app

I did not lose any files or settings (run a small node supporting archive.net)

apparently an issue since 4.6.5 according to https://www.reddit.com/r/qBittorrent/co ... upload_or/

HTH

I had exactly the same thing and positive results

TYVM for the advice :) :) :)