Transmission Openvpn Run Errors

    Hello there,


    I'm struggling with transmission with vpn container in Docker (Raspberry Pi 4).

    I pulled

    jstrader/transmission-openvpn:latest

    And confiigured like shown in this and this video. (In Portainer, so I couldn't add these:

    Code
    --network=mynet
               -p 9091:9091 
Extra arguments for special problems
  --dns 8.8.8.8 --dns 8.8.4.4
  --sysctl net.ipv6.conf.all.disable_ipv6=0 
  OPENVPN_CONFIG=CA\ Toronto

    Also added --cap-add=NET_ADMIN -d by checking it in Portainer.

    But when I run the container, the output is this: :(


    Could someone help me?


    Bests,

    Matt

    Hello Matt,


    Please see below my setting Transmission + Open VPN in one container on X64

    Note: People will advice again the use of Sharefolders for the volumes (especially on slow mainboards) but it is working for me.


    This is working for me very nicely with 2 main advantages:

    1. Transmission is available only if the VPN is OK (no need for a killswitch)

    2. When VPN go down (for any reason) the container is restarted)


    For ARM CPU there is a special docker file

    https://haugene.github.io/dock…ssion-openvpn/run-on-arm/


    I have not tested on RPI 4 but you may find this helpful


    Good luck

    Hi,


    The "code" I have posted is a "stack" to be configured in Portainer.

    If you don't use Portainer, the documentation is also listing a pure docker command:

    https://hub.docker.com/r/haugene/transmission-openvpn-proxy


    But now, I need to ask you:

    - Is your vpn already running in a container or at the OMV / OS level?

    Note:

    - for both answer my example is not good for you since my configuration is good for having "only" Transmission using the VPN.

    In my case the server is used for a lot more than Transmission and I didnt want the other applications to be penalized with the VPN decrease of network performance...

    VPN is running outside Docker, I use it to access my server from the internet without port forwarding (some security alertness).

    Usually nothing is connected to the VPN unless I'm not at home and configuring anything or using SMB.

    Then I am confused about exactly what you are trying to achieve....

    Your VPN is a VPN server that you use to connect from outside, then what exactly is Transmission suppose to be in that picture.

    Usually people use a VPN client (payed service ) to "hide" what they download with torrents....

    Can you please describe the "functional use case" you are after?

    I'm using a VPN server to reach my server from outside.

    And I wanna use a VPN client (Transmission-Vpn) to hide ip, because I'm downloading and seeding torrents.

    The point is I don't want to use VPN client for everything, just for Transmission BT.

    Yes, and sorry for the late answer, I wasn't at home.

    Log in Portainer:

    How can I change tun0 to tun1 for example?

    I think that's the problem, because a tun0 device already exists.

    Code
    Sat Apr 18 07:18:52 2020 TUN/TAP device tun0 opened,
Sat Apr 18 07:18:52 2020 TUN/TAP TX queue length set to 100,
Sat Apr 18 07:18:52 2020 /sbin/ip link set dev tun0 up mtu 1500,
Sat Apr 18 07:18:52 2020 /sbin/ip addr add dev tun0 local 10.10.1.146 peer 10.10.1.145,
Sat Apr 18 07:18:52 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.10.1.146 10.10.1.145 init,
Up script executed with tun0 1500 1553 10.10.1.146 10.10.1.145 init,
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.10.1.146,

    how do you create the container?

    with a docker commande line or by using portainer stack (docker-compose) file ?

    in any case please share this input (replacing with XXXXXX any sensitive data like your VPN username/password) so I can try to help you

    OK , I start to understand where you are .....

    My advice is to remove completely this docker and to create a stack.

    A stack is basically a file containing all the "parameters" that portainer will use to create the container.

    The good thing with the stack is that it is very easy to go back to the stack and make modifications or adjustments to the parameters and portainer will "recreate" the container.

    So all the parameters needed are remember in the stack and can be easily adjusted if needed.

    If you want to go that route, tell me and we will adjust the stack definition I gave you in my first post, to match you configuration & need.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden