search

haugene / docker-transmission-openvpn

Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
GNU General Public License v3.0
4.16k stars 1.21k forks source link

RPC daemon not binding to host IP #428

Closed abarbaccia closed 6 years ago

abarbaccia commented 6 years ago

Container was previously working but after update RPC does not seem to bind to host IP (192.168.1.115). Below are syslogs and then transmission log. Using Windscribe VPN.

Syslog: `Using OpenVPN provider: WINDSCRIBE Starting OpenVPN using config Canada-East-tcp.ovpn Setting OPENVPN credentials... adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0 Sun Feb 11 16:28:18 2018 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sun Feb 11 16:28:18 2018 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017 Sun Feb 11 16:28:18 2018 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Sun Feb 11 16:28:18 2018 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead. Sun Feb 11 16:28:18 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sun Feb 11 16:28:18 2018 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Feb 11 16:28:18 2018 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Feb 11 16:28:18 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]104.254.92.99:1194 Sun Feb 11 16:28:18 2018 Attempting to establish TCP connection with [AF_INET]104.254.92.99:1194 [nonblock] Sun Feb 11 16:28:19 2018 TCP connection established with [AF_INET]104.254.92.99:1194 Sun Feb 11 16:28:19 2018 TCP_CLIENT link local: (not bound) Sun Feb 11 16:28:19 2018 TCP_CLIENT link remote: [AF_INET]104.254.92.99:1194 Sun Feb 11 16:28:19 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Sun Feb 11 16:28:20 2018 VERIFY OK: depth=1, C=CA, ST=ON, L=Toronto, O=Windscribe Limited, OU=Operations, CN=Windscribe Node CA Sun Feb 11 16:28:20 2018 VERIFY OK: nsCertType=SERVER Sun Feb 11 16:28:20 2018 VERIFY OK: depth=0, C=CA, ST=ON, O=Windscribe Limited, OU=Operations, CN=Windscribe Node Server 4096 Sun Feb 11 16:28:21 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA Sun Feb 11 16:28:21 2018 [Windscribe Node Server 4096] Peer Connection Initiated with [AF_INET]104.254.92.99:1194 Sun Feb 11 16:28:22 2018 Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key Sun Feb 11 16:28:22 2018 Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Feb 11 16:28:22 2018 Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key Sun Feb 11 16:28:22 2018 Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication Sun Feb 11 16:28:22 2018 TUN/TAP device tun0 opened Sun Feb 11 16:28:22 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Sun Feb 11 16:28:22 2018 /sbin/ip link set dev tun0 up mtu 1500 Sun Feb 11 16:28:22 2018 /sbin/ip addr add dev tun0 10.111.44.10/23 broadcast 10.111.45.255 Sun Feb 11 16:28:22 2018 /etc/transmission/start.sh tun0 1500 1604 10.111.44.10 255.255.254.0 init Up script executed with tun0 1500 1604 10.111.44.10 255.255.254.0 init Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.111.44.10 Generating transmission settings.json from env variables sed'ing True to true

Transmission will run as

User name: root User uid: 0 User gid: 0

STARTING TRANSMISSION NO PORT UPDATER FOR THIS PROVIDER Transmission startup script complete. Sun Feb 11 16:28:22 2018 Initialization Sequence Completed`

Transmission log: [2018-02-11 16:28:23.856] Transmission 2.92 (14714) started (session.c:738) [2018-02-11 16:28:23.856] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:903) [2018-02-11 16:28:23.857] RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:903) [2018-02-11 16:28:23.857] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1110) [2018-02-11 16:28:23.857] Port Forwarding Stopped (port-forwarding.c:180) [2018-02-11 16:28:23.857] DHT Generating new id (tr-dht.c:311) [2018-02-11 16:28:23.857] Using settings from "/config/transmission-home" (daemon.c:528) [2018-02-11 16:28:23.857] Saved "/config/transmission-home/settings.json" (variant.c:1266) [2018-02-11 16:29:04.964] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:249) [2018-02-11 16:30:13.059] RPC Server Unable to bind to 192.168.1.115:9091 after 10 attempts, giving up (rpc-server.c:773)

abarbaccia commented 6 years ago

Some additional details on this. I was able to track down the combination of settings that is driving this issue.

If you set the RPC bind address to anything other than 0.0.0.0 , or , you change the PUID or GUID to anything other than root, the web UI does not bind and you cannot access.

This should be filed as a bug. It causes some challenges as files are owned by root.. I think workaround in the meantime is to set umask and then have scripts or other programs adjust permissions upon import

kingsleyadam commented 6 years ago

@abarbaccia, thank you for this! I was completely thrown off thinking it was something I did. But all I did was update the container.

I can confirm that once I changed the PUID and GUID to root everything worked perfectly. While using my own user the interface (or anything else) doesn't come up.

Edit: Reverting to 1.19 and everything is working nominal again.

haugene commented 6 years ago

Can this be closed now? This was due to the new RPC_HOST_WHITELIST property, and this is now fixed on latest. Can you still not make it work without being root?

abarbaccia commented 6 years ago

This is fixed. can close now. thanks!