New to qbittorrent - do I need to port forward to upload?

[gutterboy]

Hey guys,

I have recently migrated from the horrible uTorrent and I have gotten qBitTorrent working nicely apart from being able to upload/seed.

In uTorrent I was seeding fine, but I can't appear to upload in QBT - I'm not expert on this type of stuff, but does this mean I need to port forward the port I have set in Options -> Connections -> Port ?

I never used to do this with uTorrent - perhaps I had UPnP enabled in the settings?

Looking at my settings I already have Use UPnP... enabled under the aforementioned port setting.

Why is it not uploading?

[Switeck]

Enabling UPnP can only help *IF* your router and/or software firewall/s respond correctly to UPnP requests.
If you're using a proxy or VPN, UPnP probably should NOT be used unless explicitly supported by the proxy/VPN host company.

uTorrent may have uploaded without problems where qBitTorrent does not...because uTorrent has slightly better uTP NAT hole-punching.

If the torrents you're trying to upload on are private flagged torrents and/or on private trackers, uploading can be almost impossible for everyone.

Is qBitTorrent getting the green light/check at bottom of its window? (which means it's not firewalled)

[gutterboy]

[quote="Switeck"]
Is qBitTorrent getting the green light/check at bottom of its window? (which means it's not firewalled)
[/quote]

I'm not sure what I'm looking for - I see this:

[Switeck]

Between DHT nodes and the download speed at the bottom, it shows a little yellow symbol in your screenshot that means qBitTorrent is FIREWALLED!
Move your mouse cursor over it for more details...

[gutterboy]

I thought that may be it, but I thought I had it allowed access through my firewall - checking again, I see this:

[Switeck]

qBitTorrent needs to be given public (internet) access...and possibly private too!

You also have 2 instances of qBitTorrent there -- probably need to delete both and let the firewall detect and then allow the newest version only.

[gutterboy]

Is allowing it over public necessary?

[Switeck]

qBitTorrent will be blocked from incoming peer/seed internet access otherwise, so yes.

[gutterboy]

Well I allowed public connections but it has made no change.

[Switeck]

Sadly, there can be more than one firewall.
A sign that another firewall is probably still blocking is if qBitTorrent is still not getting the green light at bottom of its window.

[gutterboy]

I haven't installed any other firewalls, I just use the Windows one.

[Switeck]

So what you're saying is qBitTorrent gets the green light now?!

[gutterboy]

No, still no green light.

Also, I had to reinstall Windows recently and I just now reinstalled qBitTorrent, but still no luck - no green light.

Doing a quick Google I came across numerous other threads (here and on github) of people in similar situations - are you sure it is not a qBitTorrent issue itself!?

[Switeck]

Does uTorrent get incoming TCP peer/seed connections ok?
...Or is it only working well because it has proprietary NAT hole-punching via uTP STUN?

[gutterboy]

[quote="Switeck"]
Does uTorrent get incoming TCP peer/seed connections ok?
...Or is it only working well because it has proprietary NAT hole-punching via uTP STUN?
[/quote]

I think the answer to your first question is yes, I'm not using it anymore but I recall seeing a listing of the peer/seed connections; as for your second questio, I have no idea what that even means sorry