This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 82
qBittorrent not starting due to VPN issue #173
Comments
my vpn provider supports wg so tried that - again webui not accessible via 8081 but logs seem to indicate it has come up in any case 2023-04-10 09:04:35.870685 [INFO] VPN_ENABLED defined as 'yes' 2023-04-10 09:04:35.933067 [INFO] LEGACY_IPTABLES is set to '' 2023-04-10 09:04:35.995589 [INFO] Not making any changes to iptables version 2023-04-10 09:04:36.053468 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-04-10 09:04:36.118743 [INFO] VPN_TYPE defined as 'wireguard' 2023-04-10 09:04:36.192310 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf dos2unix: converting file /config/wireguard/wg0.conf to Unix format... 2023-04-10 09:04:36.260005 [INFO] VPN remote line defined as 'sx530201-wg.pointtoserver.com:51820' 2023-04-10 09:04:36.321352 [INFO] VPN_REMOTE defined as 'sx530201-wg.pointtoserver.com' 2023-04-10 09:04:36.379504 [INFO] VPN_PORT defined as '51820' 2023-04-10 09:04:36.437727 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-04-10 09:04:36.534369 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-04-10 09:04:36.592434 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-04-10 09:04:36.651592 [WARNING] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to CloudFlare and Google name servers 2023-04-10 09:04:36.712478 [INFO] Adding 1.1.1.1 to resolv.conf 2023-04-10 09:04:36.769965 [INFO] Adding 8.8.8.8 to resolv.conf 2023-04-10 09:04:36.828032 [INFO] Adding 1.0.0.1 to resolv.conf 2023-04-10 09:04:36.888360 [INFO] Adding 8.8.4.4 to resolv.conf 2023-04-10 09:04:36.945640 [INFO] PUID not defined. Defaulting to root user 2023-04-10 09:04:37.006941 [INFO] PGID not defined. Defaulting to root group 2023-04-10 09:04:37.060876 [INFO] Starting WireGuard... Warning: `/config/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 172.17.164.58 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 [#] ip -4 rule add not fwmark 51820 table 51820 [#] ip -4 rule add table main suppress_prefixlength 0 [#] iptables-restore -n 2023-04-10 09:04:37.741733 [INFO] Docker network defined as 172.17.0.0/16 2023-04-10 09:04:37.804965 [INFO] Adding 192.168.0.0/24 as route via docker eth0 2023-04-10 09:04:37.866817 [INFO] ip route defined as follows... -------------------- default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.3 192.168.0.0/24 via 172.17.0.1 dev eth0 -------------------- 2023-04-10 09:04:38.029274 [INFO] iptables defined as follows... -------------------- -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i wg0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 51820 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 51820 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -------------------- 2023-04-10 09:04:38.113381 [WARNING] ENABLE_SSL is set to '', SSL is not enabled. This could cause issues with logging if other apps use the same Cookie name (SID). 2023-04-10 09:04:38.173108 [WARNING] Removing the SSL configuration from the config file... 2023-04-10 09:04:38.233217 [INFO] A group with PGID root already exists in /etc/group within this container, nothing to do. 2023-04-10 09:04:38.290097 [INFO] An user with PUID root already exists within this container, nothing to do. 2023-04-10 09:04:38.347199 [WARNING] UMASK not defined (via -e UMASK), defaulting to '002' 2023-04-10 09:04:38.402802 [INFO] Starting qBittorrent daemon... Logging to /config/qBittorrent/data/logs/qbittorrent.log. 2023-04-10 09:04:39.504234 [INFO] Started qBittorrent daemon successfully... 2023-04-10 09:04:39.563099 [INFO] qBittorrent PID: 271 2023-04-10 09:04:39.631630 [INFO] HEALTH_CHECK_HOST is not set. For now using default host one.one.one.one 2023-04-10 09:04:39.703887 [INFO] HEALTH_CHECK_INTERVAL is not set. For now using default interval of 300 2023-04-10 09:04:39.783015 [INFO] HEALTH_CHECK_SILENT is not set. Because this variable is not set, it will be supressed by default 2023-04-10 09:04:39.838257 [WARNING] RESTART_CONTAINER not defined,(via -e RESTART_CONTAINER), defaulting to 'yes' 2023-04-10 09:04:39.893355 [INFO] HEALTH_CHECK_AMOUNT is not set. For now using default interval of 1 2023-04-10 09:04:39.947492 [INFO] HEALTH_CHECK_AMOUNT is set to 1 |
i am having the same issue, its been working for a few months and a few days ago it stopped |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi - when I turn the Off switch for VPN then qBittorrent starts and is accessible. I turn it On and it fails to start or at least is inaccessible from the port I have for it 8081
Running latest Docker Engine Version: 20.10.17 (API: 1.41)
Logs belowThe text was updated successfully, but these errors were encountered: