Docker-transmission-openvpn: Docker freezes in Starting Sequence: Initialization Sequence Completed...

[C0nvert]

System: Armlogic
OS: Coreelec with Docker

Docker Image freezes after: Initialization Sequence Completed

Uploaded log to this site:
https://paste.osmc.tv/raw/wocesoduxi

used these comments with Nordvpn as Provider

docker run --cap-add=NET_ADMIN -d \
              -v /your/storage/path/:/data \
              -v /etc/localtime:/etc/localtime:ro \
              -e CREATE_TUN_DEVICE=true \
              -e OPENVPN_PROVIDER=NORDVPN \
              -e OPENVPN_USERNAME=user \
              -e OPENVPN_PASSWORD=pass \
              -e WEBPROXY_ENABLED=false \
              -e LOCAL_NETWORK=192.168.0.0/24 \
              --log-driver json-file \
              -p 9091:9091 \
              haugene/transmission-openvpn

[C0nvert]

I got this working as a Stack in Portainer.
But container shows as healthy.
How can i fix this?

[Americanzer0]

I am having similar issues when using the Mullvad VPN; while using an unraid instance I am stuck at:

STARTING TRANSMISSION Transmission startup script complete. Wed Nov 18 11:25:30 2020 /sbin/ip route add 185.65.134.147/32 via 172.17.0.1 Wed Nov 18 11:25:30 2020 /sbin/ip route add 0.0.0.0/1 via 10.9.0.1 Wed Nov 18 11:25:30 2020 /sbin/ip route add 128.0.0.0/1 via 10.9.0.1 Wed Nov 18 11:25:30 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 Nov 18 11:25:30 2020 Initialization Sequence Completed

cannot access the web gui even though it appears to be ready to...

[haugene]

@C0nvert It looks to me like it works as intended. What is your IP though? The 192.168.1.x is much more common than 192.168.0.x space so I'm wondering if you have configured LOCAL_NETWORK wrong? If client your IP is 192.168.1.x then LOCAL_NETWORK=192.168.1.0/24 is correct. If you want to catch them both you can do LOCAL_NETWORK=192.168.0.0/16

[haugene]

The same might go for you @Americanzer0. If you're wondering about the whole LOCAL_NETWORK stuff, read my comment here https://github.com/haugene/docker-transmission-openvpn/issues/1334#issuecomment-726398297 and ask if it's still unclear.

It's also documented here: https://haugene.github.io/docker-transmission-openvpn/access/

[Americanzer0]

I was able to get transmission up and running, now I am running into needing to whitelist my IP address apparently as I still have not accessed the GUI...

I am by far a much more hardware orientated person than coding, and it's mildly frustrating to recognize your own shortcomings on trouble shooting these issues, more so when your transitioning from a Synology setup that ran without issues for years on PIA and now on Unraid everything seems to be broken (I swapped over to unraid right as PIA did their thing doing away with legacy support)....

[C0nvert]

I was able to fix it through Docker compose.
Configured it as a stack in portain.

My local network ist 192.168.80.X

Maybe you can explain me what was wrong with creating a container Docker ssh command line.

And btw if someone have issues with dnsleak on NordVPN just use NordVPNs DNS

@Americanzer0 if you want I can Post my Compose File.
Though it's similar to haugene's , but for v2 instead of v3.

I would close the issue, if you need further support, just reopen it and I'm always happy to help.

@haugene Either way a special thanks for your effort , is there a way to support you with a small donation?
Nevermind i found the Donation button.
It is not a Big amount , but at least something ))

See it as virtual Beer 😂 and big big Thank You!
Greetings from Germany ))

[haugene]

@C0nvert Glad you got it working. And thanks for your contribution. Much appreciated 🍻

As for your docker ssh command, it looks good to me. That should work. With the right LOCAL_NETWORK of course and changing /your/storage/path for a real one.