[BUG] Why doesn't bypass authentication on same subnet work? about docker-qbittorrent HOT 4 CLOSED

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

from docker-qbittorrent.

You would need to check qbit logs to see what IP it's seeing your client as. Likely your docker network is changing it https://www.pedrolamas.com/2020/11/04/exposing-the-client-ips-to-docker-containers-on-synology-nas/

from docker-qbittorrent.

You would need to check qbit logs to see what IP it's seeing your client as. Likely your docker network is changing it https://www.pedrolamas.com/2020/11/04/exposing-the-client-ips-to-docker-containers-on-synology-nas/

Thanks you were right, I am such a n00b. I used the script and re-enabled the firewall rules on the Docker container like so

• FIREWALL_OUTBOUND_SUBNETS=172.20.0.0/16,192.168.178.0/24 #change this in line with your subnet see note on guide.

My firewall is setup to allow bypass for everything locally

with a rule at the bottom that denies everything else (external IPs):

I can now access qBittorrent locally without having to authenticate, and I confirmed that it didn't expose the port externally by trying to connect over my DDNS (connection was refused).

Thanks!

from docker-qbittorrent.

forgot to close the issue.

from docker-qbittorrent.