No upload activity embedded tracker

[Rossano95]

qBittorrent version and Operating System

v4.1.5 Windows 10

What is the problem

If using embedded traker no upload activity

What is the expected behavior

Upload activity

Steps to reproduce

Create a torrent using the qbittorent tool.

Extra info(if any)

The port is open and I checked with http://www.canyouseeme.org

[Seeker2]

The embedded tracker probably "sees" your qBitTorrent as running at its LAN ip address, not its internet ip address which is what others need to connect to it.
It might work if running on the same LAN ip range or if no one is running a firewalled BitTorrent client.
Reason I believe this: 4.1.5 send internal ip to tracker if network interface selected #10051

If the torrent is flagged private, then DHT, PEX, LSD cannot run and find+link together peers+seeds.
DHT+PEX is almost a requirement to get no-tracker torrents to work.

It is possible to manually add a peer in the peers window by right-clicking, Add a Peer. -- BUT the peer must not be firewalled or it's nearly guaranteed to fail. I regularly do this in my testing.

[Rossano95]

But the strange thing is that I can access the tracker through internet. I see the tracker working but no upload activity.

[Seeker2]

Which is the problem I described. Other peers/seeds on the internet can connect to the tracker but the tracker hands out your your seed's LAN ip address not its internet ip address...so they cannot connect to your seed's LAN ip address.

Your "LAN only" seed might still eventually get the other peers'/seeds' internet address from the embedded tracker (after a tracker update) and try to connect to them.
BUT... if the other peers/seeds are firewalled in their BitTorrent client, your "LAN only" seed will always fail to connect to them. That is not a problem you can fix on your end.

[Rossano95]

So I have to wait for a fix from qbittorent? Thank you. In a previous version this worked perfectly. I hope they fix this soon.

[Seeker2]

There is a fix coming for a similar problem, but the internal tracker seeing the local peer/seed as a LAN ip only may not be fixed at the same time.

The internal tracker may have seemed to work in a previous version because some/most/all of the peers/seeds may have not been firewalled.

[Rossano95]

Ok, I will wait. Thank you

[sledgehammer999]

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.