Hi all,
I am new with OpenMediaVault and I am following the tutorials from Techno Dad Life.
Now i was following the "How to Install Transmission with VPN on Openmediavault 2019" tutorial, but I have a issue and i can't find the solution.
If I start the container and go directly to <ip omv>:9091, the Transmission GUI is showed.
If i hit F5 the page reloads until the VPN connection is established, than i loose the connection with Transmission.
I have tried many things with the network settings, but I cannot get it working.
What do i wrong?
Raspberry Pi 4
Used OMV image: OMV_4_Raspberry_Pi_2_3_3Plus_4.img.xz (4.1.23-1 Arrakis)
Docker Engine - Community
Version: 19.03.2
API version: 1.40
First i create mynet network
docker network create mynet
After that i start the container, and when the VPN connection comes up the transmission webpage is not reachable anymore
docker run --cap-add=NET_ADMIN -d \
--network mynet \
--device=/dev/net/tun \
-v /sharedfolders/Downloads/:/data:rw \
-v /sharedfolders/AppData/Transmission/:/config:rw \
-v /etc/localtime:/etc/localtime:ro \
-e "CREATE_TUN_DEVICE=true" \
-e "OPENVPN_PROVIDER=TIGER" \
-e "OPENVPN_USERNAME=username" \
-e "OPENVPN_PASSWORD=password" \
-e "OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60" \
-e "WEBPROXY_ENABLED=true" \
-e "LOCAL_NETWORK=192.168.1.0/24" \
-e "PUID=1000" \
-e "PGID=100" \
-e "CREATE_TUN_DEVICE=true" \
--log-driver json-file \
--log-opt max-size=10m \
-p 9091:9091 \
--name transmission-openvpnx \
haugene/transmission-openvpn:latest-armhf
Even when I do it through the OMV GUI I have the same problems
The container log file:
Using OpenVPN provider: TIGER
No VPN configuration provided. Using default.
Setting OPENVPN credentials...
adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0
Mon Sep 9 22:45:22 2019 OpenVPN 2.4.0 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 14 2018
Mon Sep 9 22:45:22 2019 library versions: OpenSSL 1.0.2r 26 Feb 2019, LZO 2.08
Mon Sep 9 22:45:22 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Sep 9 22:45:22 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]37.252.248.92:1194
Mon Sep 9 22:45:22 2019 UDP link local (bound): [AF_INET][undef]:1194
Mon Sep 9 22:45:22 2019 UDP link remote: [AF_INET]37.252.248.92:1194
Mon Sep 9 22:45:22 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Sep 9 22:45:22 2019 [tigervpn.com] Peer Connection Initiated with [AF_INET]37.252.248.92:1194
Mon Sep 9 22:45:24 2019 TUN/TAP device tun0 opened
Mon Sep 9 22:45:24 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Sep 9 22:45:24 2019 /sbin/ip link set dev tun0 up mtu 1500
Mon Sep 9 22:45:24 2019 /sbin/ip addr add dev tun0 100.97.0.29/16 broadcast 100.97.255.255
Mon Sep 9 22:45:24 2019 /etc/openvpn/tunnelUp.sh tun0 1500 1553 100.97.0.29 255.255.0.0 init
Up script executed with tun0 1500 1553 100.97.0.29 255.255.0.0 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 100.97.0.29
Generating transmission settings.json from env variables
sed'ing True to true
Enforcing ownership on transmission config directories
Applying permissions to transmission config directories
Setting owner for transmission paths to 1000:100
Setting permission for files (644) and directories (755)
-------------------------------------
Transmission will run as
-------------------------------------
User name: abc
User uid: 1000
User gid: 100
-------------------------------------
STARTING TRANSMISSION
NO PORT UPDATER FOR THIS PROVIDER
Transmission startup script complete.
STARTING TINYPROXY
Found config file /etc/tinyproxy/tinyproxy.conf, updating settings.
Setting tinyproxy port to 8888
Starting Tinyproxy lightweight HTTP proxy daemon: tinyproxy.
Tinyproxy startup script complete.
Mon Sep 9 22:45:29 2019 Initialization Sequence Completed