Trigus42
commented
10 months ago I've tried it and with this config it works for me:
docker-compose.yml
version: "3.3"
services:
qbittorrent:
image: trigus42/qbittorrentvpn
container_name: qbittorrent-test
environment:
...
volumes:
...
ports:
...
restart: unless-stopped
cap_add:
- NET_ADMIN
- SYS_MODULE
sysctls:
- net.ipv4.conf.all.src_valid_mark=1
- net.ipv6.conf.all.disable_ipv6=0
networks:
default:
radarr:
image: lscr.io/linuxserver/radarr:latest
container_name: radarr
environment:
- PUID=1000
- PGID=1000
ports:
...
restart: unless-stopped
networks:
default:Radarr download client config:
Host: "qbittorrent"
Port: "8080"
Username: "admin"
Password: mypasswordThat ping doesn't work is expected. You can allow pings to the container (not from the container) by running the following commands in the container:
nft "add rule inet firewall input icmp type {echo-request} accept"
nft "add rule inet firewall output icmp type {echo-reply} accept"Please try to ping the qbittorrent container from the radarr container.
You can log dropped packets by running the following commands in the container:
nft "add chain inet firewall input { type filter hook input priority 0; log prefix \"qbt-nft.firewall_input_drop \"; policy drop; }"
nft "add chain inet firewall output { type filter hook postrouting priority 0; log prefix \"qbt-nft.firewall_output_drop \"; policy drop; }"And the following command on your host:
echo 1 > /proc/sys/net/netfilter/nf_log_all_netnsNow you can see the packets being dropped by the firewall in your host's syslog.
Please post the logs of those dropped packets.
EpicLPer
Heya,
I moved my containers away from Synology and now to a proper Ubuntu Docker host (due to outdated kernel stuff), however I'm facing a weird issue right now.
I'm trying to connect from various *arr containers to qBittorrent, but no matter what I try it simply just times out after a while. The loading icon keeps spinning (both on "Test" and "Save"), after about 1-2 minutes it throws the below mentioned error in the log.
When I use a wrong port or host it instantly times out, but using the correct information it takes the above mentioned 1-2 minutes before actually timing out. The web interface works just fine, no issues there. Another thing to note is that I can't ping the qbittorrentvpn container from any of the arr containers, also vice versa. I already tried throwing all containers into a single network (or rather docker-compose), even setting it to the bridged network won't make a difference.
When I move every container back to Synology it seems to work just fine again, however I'm using build "7871e66f8529db34ac58b54e1df56d9db51cf2e5" there. Maybe something broke with a newer build lately?