docker-qBittorrentvpn
docker-qBittorrentvpn copied to clipboard
Unable to connect with port 8080
Hi,
I can't connect to the web portal on 8080.
Based on the logs, it looks like a bug
-- portainer stack includes
WEBUI_PORT_ENV=8080
-- current log does not show the port, just ends at "defined as":
2020-10-28 09:16:32.708375 [info] WebUI port defined as
-- the iptables configuration in the logs does not include port 8080 at all
Coincidentally if I change the WEBUI PORT to 9091 for testing it does not get applied to the iptables
Full log below ---
2020-10-28 09:16:26.081571 [info] VPN_ENABLED defined as 'yes'
2020-10-28 09:16:26.185324 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/london.ovpn
dos2unix: converting file /config/openvpn/london.ovpn to Unix format...
2020-10-28 09:16:26.560692 [info] VPN remote line defined as 'uk-london.privacy.network 1198'
2020-10-28 09:16:26.649084 [info] VPN_REMOTE defined as 'uk-london.privacy.network'
2020-10-28 09:16:26.740275 [info] VPN_PORT defined as '1198'
2020-10-28 09:16:26.828177 [info] VPN_PROTOCOL defined as 'udp'
2020-10-28 09:16:26.918164 [info] VPN_DEVICE_TYPE defined as 'tun0'
2020-10-28 09:16:27.003678 [info] LAN_NETWORK defined as '192.168.100.0/24'
2020-10-28 09:16:27.092215 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4,1.1.1.1,1.0.0.1'
2020-10-28 09:16:27.177308 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2020-10-28 09:16:27.263724 [info] Adding 8.8.8.8 to resolv.conf
2020-10-28 09:16:27.359544 [info] Adding 8.8.4.4 to resolv.conf
2020-10-28 09:16:27.449158 [info] Adding 1.1.1.1 to resolv.conf
2020-10-28 09:16:27.534856 [info] Adding 1.0.0.1 to resolv.conf
2020-10-28 09:16:27.614511 [info] Starting OpenVPN...
Wed Oct 28 09:16:27 2020 WARNING: file 'credentials.conf' is group or others accessibl
Wed Oct 28 09:16:27 2020 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2019
Wed Oct 28 09:16:27 2020 library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.08
Wed Oct 28 09:16:27 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]37.235.97.7:1198
Wed Oct 28 09:16:27 2020 UDP link local: (not bound)
Wed Oct 28 09:16:27 2020 UDP link remote: [AF_INET]37.235.97.7:1198
Wed Oct 28 09:16:27 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Oct 28 09:16:27 2020 [london420] Peer Connection Initiated with [AF_INET]37.235.97.7:1198
Wed Oct 28 09:16:28 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Wed Oct 28 09:16:28 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3
Wed Oct 28 09:16:28 2020 TUN/TAP device tun0 opened
Wed Oct 28 09:16:28 2020 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Wed Oct 28 09:16:28 2020 /sbin/ip link set dev tun0 up mtu 1500
Wed Oct 28 09:16:28 2020 /sbin/ip addr add dev tun0 10.60.112.6/24 broadcast 10.60.112.255
Wed Oct 28 09:16:28 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.
Wed Oct 28 09:16:28 2020 Initialization Sequence Completed
2020-10-28 09:16:32.708375 [info] WebUI port defined as
2020-10-28 09:16:32.793778 [info] LAN Network defined as 192.168.100.0/24
2020-10-28 09:16:32.878585 [info] Default gateway defined as 172.19.0.1
2020-10-28 09:16:32.962200 [info] ip route defined as follows...
0.0.0.0/1 via 10.60.112.1 dev tun0
default via 172.19.0.1 dev eth0
10.60.112.0/24 dev tun0 proto kernel scope link src 10.60.112.6
37.235.97.7 via 172.19.0.1 dev eth0
128.0.0.0/1 via 10.60.112.1 dev tun0
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2
192.168.100.0/24 via 172.19.0.1 dev eth0
iptable_mangle 16384 0
ip_tables 32768 3 iptable_filter,iptable_raw,iptable_mangle
x_tables 53248 13 xt_conntrack,iptable_filter,nft_compat,xt_tcpudp,xt_addrtype,xt_nat,xt_comment,xt_connmark,iptable_raw,ip_tables,xt_MASQUERADE,iptable_mangle,xt_mark
2020-10-28 09:16:33.068391 [info] iptable_mangle support detected, adding fwmark for tables
2020-10-28 09:16:33.215032 [info] Docker network defined as 172.19.0.0/16
2020-10-28 09:16:33.406898 [info] iptables defined as follows...
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -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 -s 192.168.100.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -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 -d 192.168.100.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
Adding 0 group
groupadd: GID '0' already exists
Adding 0 user
useradd: UID 0 is not unique
2020-10-28 09:16:33.547344 [info] UMASK defined as '777'
2020-10-28 09:16:33.626286 [info] Starting qBittorrent daemon...
Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log.
2020-10-28 09:16:34.735489 [info] qBittorrent PID:
2020-10-28 09:16:34.784089 [info] Started qBittorrent daemon successfully...
Another issue thread had a fix for my problem. Need to use "WEBUI_PORT" instead of "WEBUI_PORT_ENV" .
I have the same issue as above. Tried using the WEBUI_PORT environment variable as well but that did not help. Has anyone has any other suggestions?
[UPDATE] Figured out the issue. I am using a VLAN in the server and was not able to access from other VLANs. Tried within the same VLAN and it works. Now I need to figure out to how to get it working in all the VLANs
I have the same issue as above. Tried using the WEBUI_PORT environment variable as well but that did not help. Has anyone has any other suggestions?
[UPDATE] Figured out the issue. I am using a VLAN in the server and was not able to access from other VLANs. Tried within the same VLAN and it works. Now I need to figure out to how to get it working in all the VLANs
Did you ever figure that out?
I updated my rules to allow for the main LAN to be able to access this particular system and it works.