Jump to content

bumperjeep

Members
  • Posts

    39
  • Joined

  • Last visited

Posts posted by bumperjeep

  1. Hi - I have a routing question. I'm thinking of doing a site to site vpn on my router. I wanted to make sure that there wasn't anything I could do at my router level that would override / mess up the iptables on the container. I'm referring to the iptable rules you describe here https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md.

     

    I'm sure that PIA uses a 10. network internally, and my site to site might also be joining to a remote 10. network. The container does not need to talk to the remote network ever, so I'm just double checking I won't break your core functionality.

     

  2. Hi I've been using the rtorrent container for a while, but switched here since it got deprecated.

     

    my default save path is /media/red, but it's pretty low on space, so I wanted to save some torrents to /media/blue.

    I set the save location when adding the torrent, but it keeps on downloading to red and only moving to blue when it's finished. Is there a way to avoid this behavior? For this specific torrent, I only want to write to blue. I know you could definitely do that with rtorrent, but I can't seem to figure that out with qbit. Thanks!

  3. So I added the following to my rtorrent.rc,

    execute = {/bin/bash,-c,mkdir -p /config/rtorrent/logs}
    log.open_file = "rtorrent", /config/rtorrent/logs/rtorrent.log
    log.open_file = "tracker", /config/rtorrent/logs/tracker.log
    log.open_file = "storage", /config/rtorrent/logs/storage.log
    
    # rTorrent logging verbosity for rtorrent, comment out if logs are too chatty
    log.add_output = "info", "rtorrent"
    log.add_output = "critical", "rtorrent"
    log.add_output = "error", "rtorrent"
    log.add_output = "warn", "rtorrent"
    log.add_output = "notice", "rtorrent"
    log.add_output = "debug", "rtorrent"
    
    # rTorrent logging for dht and tracker traffic
    log.add_output = "dht_debug", "tracker"
    log.add_output = "tracker_debug", "tracker"
    
    # rTorrent logging for storage
    log.add_output = "storage_debug", "storage"

    that wrote logs and told me that this line

    execute = {/bin/bash,-c,mkdir -p /data/incomplete}

    is causing the error. I never had a mount for /data, that line has always been there. I have no idea why all of a sudden it's been a problem. Might be cool to add those logs to supervisord.log. Anyway, I hope this helps somebody else!

  4. Hi - I just unpinned my Rtorrent version to pull latest, from

    image: binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28

    I'm having a bit of trouble understanding the changes needed in questions 25 and 26. I'm using Sonarr, Radarr and Jackett. Sonarr and Radarr are configured to use Jackett as a provider, but I also had an HTTPS proxy configured for Sonarr and Radarr. I'm using Ubuntu with docker compose. I'm only accessing the web ui for these apps via a VPN (wireguard hosted on this server). My main issue is that torrents from Jackett are not downloading once added to rtorrent

     

    Do I need to change or add values?

    VPN_OUTPUT_PORTS

    VPN_INPUT_PORTS

    - LAN_NETWORK=192.168.55.0/24,10.6.0.0/24 (LAN, Wireguard home vpn subnets)

     

    I'll try reading the instructions again.

    I'm also using 9443 for the web port instead of 9080  from the issues a few weeks ago.

     

    Since I'm  using docker compose, do I need to add networks to my config? I don't have that set up. I can see all of the UIs for the apps, but now no torrents will download.

     

     

    EDIT:

     

    I did a little more research and when I download the .torrent directly from Jackett and add it myself to rtorrent, the downloads start in rtorrent, when sonarr adds the torrent to jackett, they don't.

  5. I've been using this container for years, and I've been running into a lot of issues lately. I've pinned the container to the last working version: binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-28

     

    For some reason, it's failing to start rtorrent. I did a dist upgrade from Ubuntu 18.04 and 20.04 a few weeks ago and I'm not sure if that's part of it. What else can I look through if Rtorrent is failing to start? Is there another log?

     

    I'm also getting this error:

     Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken'

     

     

    I'm also getting this a minutes after the last healthy log message:

    2021-02-12 03:48:05,459 WARN received SIGTERM indicating exit request

     

  6. 11 hours ago, binhex said:

    OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).

     

    What this means is that the image will now loop through the entire list, for example, pia port forward enabled endpoints, all you need to do is edit your ovpn config file and add the remote endpoints at the top and sort into the order you want them to be tried, an example pia ovpn file is below (mine):-

    
    remote ca-toronto.privateinternetaccess.com 1198 udp
    remote ca-montreal.privateinternetaccess.com 1198 udp
    remote ca-vancouver.privateinternetaccess.com 1198 udp
    remote de-berlin.privateinternetaccess.com 1198 udp
    remote de-frankfurt.privateinternetaccess.com 1198 udp
    remote france.privateinternetaccess.com 1198 udp
    remote czech.privateinternetaccess.com 1198 udp
    remote spain.privateinternetaccess.com 1198 udp
    remote ro.privateinternetaccess.com 1198 udp
    client
    dev tun
    resolv-retry infinite
    nobind
    persist-key
    # -----faster GCM-----
    cipher aes-128-gcm
    auth sha256
    ncp-disable
    # -----faster GCM-----
    tls-client
    remote-cert-tls server
    auth-user-pass credentials.conf
    comp-lzo
    verb 1
    crl-verify crl.rsa.2048.pem
    ca ca.rsa.2048.crt
    disable-occ

     

    I did look at multi ovpn file support, but this is easier to do and as openvpn supports multi remote lines, it felt like the most logical approach.

     

    note:- Due to ns lookup for all remote lines, and potential failure and subsequent try of the next remote line, time to initialisation of the app may take longer.

     

    p.s. I dont want to talk about how difficult this was to shoe horn in, i need to lie down in a dark room now and not think about bash for a while :-), any issues let me know!.

    Haha i'm looking at the code https://github.com/binhex/arch-rtorrentvpn/commit/4aeb0bb40542d8450bfb21dcc1c16978c6640ff0

    I see what you mean, this would have been much easier with a real programming language. Python would have worked perfectly for this. Anyway, thanks for your help. I managed to get it working a week ago and it hasn't disconnected since so I plan on updating when it goes down, thank!

    • Thanks 1
  7. Hi, long time user here:

    My container is getting stuck here and isn't coming back up. I've waited about 10 minutes. Any idea?

     

    2019-11-28 13:32:55,119 DEBG 'watchdog-script' stdout output:
    [info] rTorrent not running

    2019-11-28 13:32:55,124 DEBG 'watchdog-script' stdout output:
    [info] Privoxy not running

    2019-11-28 13:32:55,124 DEBG 'watchdog-script' stdout output:
    [info] rTorrent incoming port 49160 and VPN incoming port 48349 different, marking for reconfigure

    2019-11-28 13:32:55,124 DEBG 'watchdog-script' stdout output:
    [info] Removing any rTorrent session lock files left over from the previous run...

    2019-11-28 13:32:55,126 DEBG 'watchdog-script' stdout output:
    [info] Attempting to start rTorrent...

    2019-11-28 13:32:55,127 DEBG 'watchdog-script' stdout output:
    Script started, file is /home/nobody/typescript

    2019-11-28 13:32:55,144 DEBG 'watchdog-script' stdout output:
    Script done, file is /home/nobody/typescript

  8. @binhex Do you have any ideas on the modprobe errors - modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-131-generic

     

    My container wasn't loading rtorrent last night, had a lot of issues. Didn't see anything obvious in supervisor.log other than the modprobe errors. I also looked at the FAQs in your signature. 

  9. On 8/4/2018 at 7:01 PM, bumperjeep said:

    So I removed the rtorrent.rc file, the container and started the container again, and it still doesn't come back up. Here is the full logs. 

     

     

    
    Created by...
    ___.   .__       .__
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    <
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    2018-08-04 18:56:11.319555 [info] System information Linux 8dd3c06831be 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 GNU/Linux
    2018-08-04 18:56:11.361603 [info] PUID defined as '1000'
    2018-08-04 18:56:11.451168 [info] PGID defined as '1000'
    2018-08-04 18:56:11.502370 [info] UMASK defined as '000'
    2018-08-04 18:56:11.542956 [info] Permissions already set for volume mappings
    2018-08-04 18:56:11.588439 [info] VPN_ENABLED defined as 'yes'
    2018-08-04 18:56:11.635162 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn
    dos2unix: converting file /config/openvpn/CA Toronto.ovpn to Unix format...
    2018-08-04 18:56:11.694563 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
    2018-08-04 18:56:11.735606 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
    2018-08-04 18:56:11.777282 [info] VPN_PORT defined as '1198'
    2018-08-04 18:56:11.822301 [info] VPN_PROTOCOL defined as 'udp'
    2018-08-04 18:56:11.863818 [info] VPN_DEVICE_TYPE defined as 'tun0'
    2018-08-04 18:56:11.905185 [info] VPN_PROV defined as 'pia'
    2018-08-04 18:56:11.946579 [info] LAN_NETWORK defined as '10.10.10.0/24'
    2018-08-04 18:56:11.987852 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
    2018-08-04 18:56:12.111140 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
    2018-08-04 18:56:12.151911 [info] STRICT_PORT_FORWARD defined as 'yes'
    2018-08-04 18:56:12.192809 [info] ENABLE_PRIVOXY defined as 'yes'
    2018-08-04 18:56:12.233986 [info] ENABLE_FLOOD defined as 'no'
    2018-08-04 18:56:12.275712 [info] ENABLE_AUTODL_IRSSI defined as 'yes'
    2018-08-04 18:56:29.726221 [info] Starting Supervisor...
    2018-08-04 18:56:29,929 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing
    2018-08-04 18:56:29,929 INFO Set uid to user 0 succeeded
    2018-08-04 18:56:29,933 INFO supervisord started with pid 8
    2018-08-04 18:56:30,935 INFO spawned: 'start-script' with pid 153
    2018-08-04 18:56:30,937 INFO spawned: 'rutorrent-script' with pid 154
    2018-08-04 18:56:30,939 INFO spawned: 'flood-script' with pid 155
    2018-08-04 18:56:30,941 INFO spawned: 'irssi-script' with pid 156
    2018-08-04 18:56:30,943 INFO spawned: 'rtorrent-script' with pid 157
    2018-08-04 18:56:30,945 INFO spawned: 'privoxy-script' with pid 159
    2018-08-04 18:56:30,946 INFO reaped unknown pid 9
    2018-08-04 18:56:30,947 DEBG 'start-script' stdout output:
    [info] VPN is enabled, beginning configuration of VPN
    
    2018-08-04 18:56:30,947 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,947 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,947 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,947 INFO success: irssi-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,947 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,947 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2018-08-04 18:56:30,957 DEBG 'flood-script' stdout output:
    [info] Flood not enabled, skipping starting Flood Web UI
    
    2018-08-04 18:56:30,958 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 139685100496800 for <Subprocess at 139685100516776 with name flood-script in state RUNNING> (stdout)>
    2018-08-04 18:56:30,958 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 139685100497016 for <Subprocess at 139685100516776 with name flood-script in state RUNNING> (stderr)>
    2018-08-04 18:56:30,958 INFO exited: flood-script (exit status 0; expected)
    2018-08-04 18:56:30,958 DEBG received SIGCLD indicating a child quit
    2018-08-04 18:56:30,970 DEBG 'rtorrent-script' stdout output:
    [info] rTorrent config file doesnt exist, copying default to /config/rtorrent/config/...
    
    2018-08-04 18:56:30,999 DEBG 'rtorrent-script' stderr output:
    dos2unix: converting file /config/rtorrent/config/rtorrent.rc to Unix format...
    
    2018-08-04 18:56:31,001 DEBG 'rtorrent-script' stdout output:
    [info] VPN is enabled, checking VPN tunnel local ip is valid
    
    2018-08-04 18:56:31,036 DEBG 'start-script' stdout output:
    [info] Default route for container is 172.19.0.1
    
    2018-08-04 18:56:31,041 DEBG 'start-script' stdout output:
    [info] Adding 8.8.8.8 to /etc/resolv.conf
    
    2018-08-04 18:56:31,046 DEBG 'start-script' stdout output:
    [info] Adding 8.8.4.4 to /etc/resolv.conf
    
    2018-08-04 18:56:31,085 DEBG 'start-script' stdout output:
    [info] Attempting to load tun kernel module...
    
    2018-08-04 18:56:31,089 DEBG 'start-script' stderr output:
    modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-131-generic
    
    2018-08-04 18:56:31,090 DEBG 'start-script' stdout output:
    [warn] Unable to load tun kernel module using modprobe, trying insmod...
    
    2018-08-04 18:56:31,091 DEBG 'start-script' stdout output:
    [warn] Unable to load tun kernel module, assuming its dynamically loaded
    
    2018-08-04 18:56:31,091 DEBG 'start-script' stderr output:
    insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory
    
    2018-08-04 18:56:31,106 DEBG 'start-script' stdout output:
    [info] Adding 10.10.10.0/24 as route via docker eth0
    
    2018-08-04 18:56:31,108 DEBG 'start-script' stdout output:
    [info] ip route defined as follows...
    --------------------
    
    2018-08-04 18:56:31,110 DEBG 'start-script' stdout output:
    default via 172.19.0.1 dev eth0
    10.10.10.0/24 via 172.19.0.1 dev eth0
    172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2
    --------------------
    
    2018-08-04 18:56:31,120 DEBG 'start-script' stdout output:
    iptable_mangle         16384  0
    ip_tables              24576  3 iptable_filter,iptable_mangle,iptable_nat
    x_tables               36864  21 xt_DSCP,xt_dscp,xt_mark,xt_hl,xt_helper,xt_length,ip_tables,xt_tcpmss,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_nat,iptable_filter,xt_TCPMSS,ipt_REJECT,xt_REDIRECT,iptable_mangle,xt_addrtype
    
    2018-08-04 18:56:31,121 DEBG 'start-script' stdout output:
    [info] iptable_mangle support detected, adding fwmark for tables
    
    2018-08-04 18:56:31,157 DEBG 'start-script' stdout output:
    [info] Docker network defined as    172.19.0.0/16
    
    2018-08-04 18:56:31,255 DEBG 'start-script' stdout output:
    [info] iptables defined as follows...
    --------------------
    
    2018-08-04 18:56:31,258 DEBG 'start-script' stdout output:
    -P INPUT DROP
    -P FORWARD ACCEPT
    -P OUTPUT DROP
    -A INPUT -i tun0 -j ACCEPT
    -A INPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
    -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
    -A INPUT -s 10.10.10.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT
    -A INPUT -s 10.10.10.0/24 -d 172.19.0.0/16 -i eth0 -p tcp -j ACCEPT
    -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A OUTPUT -o tun0 -j ACCEPT
    -A OUTPUT -s 172.19.0.0/16 -d 172.19.0.0/16 -j ACCEPT
    -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT
    -A OUTPUT -d 10.10.10.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT
    -A OUTPUT -s 172.19.0.0/16 -d 10.10.10.0/24 -o eth0 -p tcp -j ACCEPT
    -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
    -A OUTPUT -o lo -j ACCEPT
    
    2018-08-04 18:56:31,258 DEBG 'start-script' stdout output:
    --------------------
    
    2018-08-04 18:56:31,259 DEBG 'start-script' stdout output:
    [info] Starting OpenVPN...
    
    2018-08-04 18:56:31,268 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:31 2018 WARNING: file 'credentials.conf' is group or others accessible
    Sat Aug  4 18:56:31 2018 OpenVPN 2.4.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar  1 2018
    Sat Aug  4 18:56:31 2018 library versions: OpenSSL 1.1.0g  2 Nov 2017, LZO 2.10
    
    2018-08-04 18:56:31,271 DEBG 'start-script' stdout output:
    [info] OpenVPN started
    Sat Aug  4 18:56:31 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
    Sat Aug  4 18:56:31 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.82:1198
    Sat Aug  4 18:56:31 2018 UDP link local: (not bound)
    Sat Aug  4 18:56:31 2018 UDP link remote: [AF_INET]172.98.67.82:1198
    
    2018-08-04 18:56:31,384 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:31 2018 [74e9e038cc1ee5f11e97abf6aba60f3a] Peer Connection Initiated with [AF_INET]zzz
    
    2018-08-04 18:56:32,590 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:32 2018 auth-token received, disabling auth-nocache for the authentication token
    
    2018-08-04 18:56:32,590 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:32 2018 TUN/TAP device tun0 opened
    Sat Aug  4 18:56:32 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
    Sat Aug  4 18:56:32 2018 /usr/bin/ip link set dev tun0 up mtu 1500
    
    2018-08-04 18:56:32,593 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:32 2018 /usr/bin/ip addr add dev tun0 local 10.66.10.6 peer 10.66.10.5
    
    2018-08-04 18:56:32,594 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:32 2018 /root/openvpnup.sh tun0 1500 1558 10.66.10.6 10.66.10.5 init
    
    2018-08-04 18:56:32,609 DEBG 'start-script' stdout output:
    Sat Aug  4 18:56:32 2018 Initialization Sequence Completed
    
    2018-08-04 18:56:32,633 DEBG 'privoxy-script' stdout output:
    [info] Configuring Privoxy...
    
    2018-08-04 18:56:32,642 DEBG 'rtorrent-script' stdout output:
    [info] rTorrent not running
    [info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.66.10.6 different, marking for reconfigure
    
    2018-08-04 18:56:32,658 DEBG 'privoxy-script' stdout output:
    [info] All checks complete, starting Privoxy...
    
    2018-08-04 18:56:32,659 DEBG 'privoxy-script' stderr output:
    2018-08-04 18:56:32.659 7f7bd9f8d0c0 Info: Privoxy version 3.0.26
    2018-08-04 18:56:32.659 7f7bd9f8d0c0 Info: Program name: /usr/bin/privoxy
    
    2018-08-04 18:56:32,729 DEBG 'irssi-script' stdout output:
    Script started, file is /home/nobody/typescript
    
    2018-08-04 18:56:32,738 DEBG 'start-script' stdout output:
    [info] Attempting to curl http://209.222.18.222:2000/?client_id=UUID...
    
    2018-08-04 18:56:32,756 DEBG 'irssi-script' stdout output:
    Script done, file is /home/nobody/typescript
    
    2018-08-04 18:56:32,763 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 139685100496008 for <Subprocess at 139685100516632 with name irssi-script in state RUNNING> (stdout)>
    2018-08-04 18:56:32,763 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 139685100461520 for <Subprocess at 139685100516632 with name irssi-script in state RUNNING> (stderr)>
    2018-08-04 18:56:32,763 INFO exited: irssi-script (exit status 0; expected)
    2018-08-04 18:56:32,763 DEBG received SIGCLD indicating a child quit
    2018-08-04 18:56:32,843 DEBG 'start-script' stdout output:
    [info] Successfully retrieved external IP address 
    
    2018-08-04 18:56:33,997 DEBG 'start-script' stdout output:
    [info] Curl successful for http://209.222.18.222:2000/?client_id=UUID, response code 200
    
    2018-08-04 18:56:34,852 DEBG 'rtorrent-script' stdout output:
    [info] Removing any rTorrent session lock files left over from the previous run...
    
    2018-08-04 18:56:34,855 DEBG 'rtorrent-script' stdout output:
    [info] Attempting to start rTorrent...
    
    2018-08-04 18:56:34,856 DEBG 'rtorrent-script' stdout output:
    Script started, file is /home/nobody/typescript
    
    2018-08-04 18:56:34,879 DEBG 'rtorrent-script' stdout output:
    Script done, file is /home/nobody/typescript
    
    2018-08-04 18:56:35,010 DEBG 'rtorrent-script' stdout output:
    Script started, file is /home/nobody/typescript
    
    2018-08-04 18:56:35,022 DEBG 'rtorrent-script' stdout output:
    duplicate session: irssi_session
    
    2018-08-04 18:56:35,032 DEBG 'rtorrent-script' stdout output:
    Script done, file is /home/nobody/typescript
    

     

    I'm getting the modprobe errors again and I completed removed the persistent container data and restarted like you suggested. Am I missing something? I haven't rebooted this machine in about 100 days, could that be the issue

  10. Here is what I did to fix this - it doesn't make sense, but it works and it took me about 2 hrs. 

     

    1. stop broken container

    2. mv the persistent data store to a folder the container is not watching. mv /opt/docker/rtorrent /opt/docker/rtorrent_save OR restore the persisent folder from backup using older docker image

    3. recreate the blank container directory - use the same user and the container pid.

    4. edit the compose file to point to an older docker tag - I think somebody had the tip for that above in unraid

    5. start the container (WITHOUT SESSION DATA) - it'll probably fail because you don't have vpn there

    6. add vpn back

    7. make sure that you can see rutorrent, but with no torrent session data.  this step was always important and has worked for me in the past. 

    8. switch the persisent folders back to the original - or restore that from a backup before the container was updated

     

     

     

     

×
×
  • Create New...