Cant downlead with Transmissionvpn but I can seed

  • It was working fine. Turned off my NAS while away on vacation and now I cant download. Everything stays on magnitized downloads but I am able to seed. Heres my logs:


    Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop

    Setting OpenVPN credentials...

    adding route to local network 192.168.1.0/24 via 172.18.0.1 dev eth0

    Fri Sep 2 23:34:48 2022 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 22 2022

    Fri Sep 2 23:34:48 2022 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10

    Fri Sep 2 23:34:48 2022 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

    Fri Sep 2 23:34:48 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]179.61.228.51:1198

    Fri Sep 2 23:34:48 2022 Socket Buffers: R=[212992->212992] S=[212992->212992]

    Fri Sep 2 23:34:48 2022 UDP link local: (not bound)

    Fri Sep 2 23:34:48 2022 UDP link remote: [AF_INET]179.61.228.51:1198

    Fri Sep 2 23:34:48 2022 TLS: Initial packet from [AF_INET]179.61.228.51:1198, sid=3222d396 fb73ff59

    Fri Sep 2 23:34:48 2022 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

    Fri Sep 2 23:34:48 2022 VERIFY OK: depth=1, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=Private Internet Access, name=Private Internet Access, emailAddress=secure@privateinternetaccess.com

    Fri Sep 2 23:34:48 2022 VERIFY KU OK

    Fri Sep 2 23:34:48 2022 Validating certificate extended key usage

    Fri Sep 2 23:34:48 2022 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication

    Fri Sep 2 23:34:48 2022 VERIFY EKU OK

    Fri Sep 2 23:34:48 2022 VERIFY OK: depth=0, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=perth403, name=perth403

    Fri Sep 2 23:34:49 2022 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA

    Fri Sep 2 23:34:49 2022 [perth403] Peer Connection Initiated with [AF_INET]179.61.228.51:1198

    Fri Sep 2 23:34:50 2022 SENT CONTROL [perth403]: 'PUSH_REQUEST' (status=1)

    Fri Sep 2 23:34:50 2022 PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway def1,route-ipv6 2000::/3,dhcp-option DNS 10.0.0.243,route-gateway 10.50.112.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.50.112.127 255.255.255.0,peer-id 1,cipher AES-128-GCM'

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: timers and/or timeouts modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: compression parms modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: --ifconfig/up options modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: route options modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: route-related options modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: peer-id set

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: adjusting link_mtu to 1625

    Fri Sep 2 23:34:50 2022 OPTIONS IMPORT: data channel crypto options modified

    Fri Sep 2 23:34:50 2022 Data Channel: using negotiated cipher 'AES-128-GCM'

    Fri Sep 2 23:34:50 2022 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key

    Fri Sep 2 23:34:50 2022 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key

    Fri Sep 2 23:34:50 2022 ROUTE_GATEWAY 172.18.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:12:00:02

    Fri Sep 2 23:34:50 2022 GDG6: remote_host_ipv6=n/a

    Fri Sep 2 23:34:50 2022 ROUTE6: default_gateway=UNDEF

    Fri Sep 2 23:34:50 2022 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

    Fri Sep 2 23:34:50 2022 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3

    Fri Sep 2 23:34:50 2022 TUN/TAP device tun0 opened

    Fri Sep 2 23:34:50 2022 TUN/TAP TX queue length set to 100

    Fri Sep 2 23:34:50 2022 /sbin/ip link set dev tun0 up mtu 1500

    Fri Sep 2 23:34:50 2022 /sbin/ip addr add dev tun0 10.50.112.127/24 broadcast 10.50.112.255

    Fri Sep 2 23:34:50 2022 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.50.112.127 255.255.255.0 init

    Up script executed with tun0 1500 1553 10.50.112.127 255.255.255.0 init

    Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.50.112.127

    Updating Transmission settings.json with values from env variables

    Using existing settings.json for Transmission /config/settings.json

    Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.50.112.127

    Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /storage/downloads/completed

    Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /storage/downloads/incomplete

    Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091

    Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /storage/downloads/watch

    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 permissions for download and incomplete directories

    2

    Directories: 775

    Files: 664

    Setting permission for watch directory (775) and its files (664)


    -------------------------------------

    Transmission will run as

    -------------------------------------

    User name: abc

    User uid: 1000

    User gid: 100

    -------------------------------------


    STARTING TRANSMISSION

    Provider PIA has a script for automatic port forwarding. Will run it now.

    If you want to disable this, set environment variable DISABLE_PORT_UPDATER=true

    Transmission startup script complete.

    Fri Sep 2 23:35:22 2022 /sbin/ip route add 179.61.228.51/32 via 172.18.0.1

    Fri Sep 2 23:35:22 2022 /sbin/ip route add 0.0.0.0/1 via 10.50.112.1

    Fri Sep 2 23:35:22 2022 /sbin/ip route add 128.0.0.0/1 via 10.50.112.1

    Fri Sep 2 23:35:22 2022 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.

    Fri Sep 2 23:35:22 2022 Initialization Sequence Completed

    Running functions for token based port fowarding

    Reserved Port: 44075 Fri Sep 2 23:35:31 CDT 2022

    transmission auth not required

    waiting for transmission to become responsive

    transmission became responsive

    3282* 100% 3.51 GB Done 0.0 0.0 0.0 Stopped Becky (2020) (1080p BluRay x265 HEVC 10bit AAC 5.1 Tigole)

    Sum: 16.62 TB 0.0 0.0

    setting transmission port to 44075

    localhost:9091/transmission/rpc/ responded: "success"

    Checking port...

    Port is open: Yes

    #######################

    SUCCESS

    #######################

    Port: 44075

    Expiration Fri Nov 4 11:20:13 CDT 2022

    #######################

    Entering infinite while loop

    Every 15 minutes, check port status

    Reserved Port: 44075 Fri Sep 2 23:51:01 CDT 2022

    • Offizieller Beitrag
    Code
      Been a while since ive done this. Whats the best way to post? Copy and paste seems to make a mess because its a whole lot of  text.

    the easiest way to do it... is create a codebox (like you did there)


    and then paste the compose in side a codebox


    or you can put it in a pastebin at pastebin.com, and give me the link. whatever works for you..


    just make sure you remove your PIA password and username whichever you do.

    • Offizieller Beitrag

    holy cow... where did you get that compose file?...


    I think the problem is your container paths... I remember something weird and it's paths and permission issues.


    I'll post my PIA compose for haugene in the morning when I get home.

    • Offizieller Beitrag

    Try deleting your old container, and adding this to your stacks and deploy it. Only thing you should need to adjust is your PIA username/password, your /data volume, and the server you want to use (this one is using us_florida)


    For a full list of the servers available for PIA in this container...


    1. Bash into the container (below assumes your transmission container is named "transvpn" as I did in that stack)


    Code
    docker exec -it transvpn bash


    2. Once bashed in

    Code
    cd /etc/openvpn/pia


    3. Then use ls and you'll see all the PIA servers included with this container.

  • I did the stack and it says healthy but not running. I had the /data set to my old transmissionvpn folder so my unfinished downloads would finish but for some reason it made a completely new transmission folder. Here is what it says in logs


    https://pastebin.com/eCAGSJjS


    edit: its working based off the fl vpn. I can download but hopefully im protected by my vpn lol. How can I get it to use my old folder? Now I have my original downloads completed and incomplete folder and my old one. I want to be able to use the old folders to finish pending downloads and to know what ive already downloaded.

    • Offizieller Beitrag

    edit: its working based off the fl vpn. I can download but hopefully im protected by my vpn lol. How can I get it to use my old folder? Now I have my original downloads completed and incomplete folder and my old one. I want to be able to use the old folders to finish pending downloads and to know what ive already downloaded.

    Testing the VPN is easy. The container has a built in kill switch, where if it's not connected to the VPN, it simply restarts itself about every 15sec. Easy way to test this, go to your stack, and change your VPN password to something that is obviously wrong.. then redeploy the stack. Watch your container log and you'll see what I'm talking about.


    Another easy test.. (the below assumes the rest of your server is not behind a VPN)


    1. SSH your server and execute this command. (alternatively, you could use one of your network machines that is not behind a VPN, and go to whatismyip.com to get your public IP)

    Code
    host myip.opendns.com resolver1.opendns.com

    Again, assuming the rest of your server is not behind the VPN, this will return your public IP.


    2. Now, execute the following command (again, this assumes the container is named transvpn).


    Code
    docker exec -it transvpn host myip.opendns.com resolver1.opendns.com

    That will return the public IP address for the container. If they are different, then the VPN is working.


    Obviously my server has a different public IP than my container, so the VPN is working.


    As for your seeding question can't really answer that. You could try messing with your volume paths a bit, but I always had permission issues with that container when I moved away from the what is more or less default.

  • Its confusing. Even the folder Have pointed to store finished downloads isnt being used. Instead its going to /data/completed when it should go to downloads


    Edit: There is still an issue I cna only dl somethings. Even things with lots of seeds will get stuck and not dl also my speed is slow like 1 mb.

    • Offizieller Beitrag

    Its confusing. Even the folder Have pointed to store finished downloads isnt being used. Instead its going to /data/completed when it should go to downloads


    Edit: There is still an issue I cna only dl somethings. Even things with lots of seeds will get stuck and not dl also my speed is slow like 1 mb.

    How do you have the folders mapped in your docker-compose?


    Can't explain your download speeds... I have zero issues there. Maybe try a different server. As for it "getting stuck".. no idea on that one.

  • KM0201

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

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