I have been using this config for qBittorrent for awhile and been working for the most part. Sometimes it gets “connection status: Firewalled” I would fix this by going to settings -> connection and click the “Random” button a couple times and save and then it would work again. This seems to not work anymore. Is there a better fix for this? Back before I used docker I don’t remember ever having to do this. I have never done any kind of manual port forwarding my current VPN provider does not do that at the price I have it for right now. Let me know if you need more information about my setup or something
Thanks
I guess it is just randomly breaks for now since it appears to be back.
Not sure why you would sometimes see your status as fully connectable
One side of the connection needs a public address, not both. When both parties don’t have a publicly addressable IP, the status is firewalled. I guess.
You might be confusing public IP addresses with ports? If your torrent client doesn’t have a public IP address that just means it’s offline / no internet. Maybe your internet is down or the VPN is disconnected. You’re won’t torrent anything at all in that state.
One side of the connection needs a public addressopen port, not both. When both parties don’t have a publicly addressable IPopen port, the status is firewalled. I guessthey can “see” each other but are unable to exchange any torrent data.
For what it’s worth in the situation where both peers don’t have open ports (meaning they are both firewalled) they end up having to wait for another peer to join that torrent swarm that happens to have a open port, that’s the only way any data will exchange in that swarm. Until that happens those two peers will sit there waiting and not exchanging data.
You might be confusing public IP addresses with ports?
I mean publicly addressable address like in: not in a private network where SNAT/ masquerading is in place between the torrent-client’s host and the Internet.
It was mentioned, that no port forwarding is in place.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
One side of the connection needs a public address, not both. When both parties don’t have a publicly addressable IP, the status is firewalled. I guess.
You might be confusing public IP addresses with ports? If your torrent client doesn’t have a public IP address that just means it’s offline / no internet. Maybe your internet is down or the VPN is disconnected. You’re won’t torrent anything at all in that state.
For what it’s worth in the situation where both peers don’t have open ports (meaning they are both firewalled) they end up having to wait for another peer to join that torrent swarm that happens to have a open port, that’s the only way any data will exchange in that swarm. Until that happens those two peers will sit there waiting and not exchanging data.
I mean publicly addressable address like in: not in a private network where SNAT/ masquerading is in place between the torrent-client’s host and the Internet.
It was mentioned, that no port forwarding is in place.