[Support] Clowrym's Docker Repository


clowrym

Recommended Posts

Oh wow, it's really been while since i posted. Anyhow, i started having issues with my privoxy, although I think i'm the only one using it lol. I'm getting this problem and I know for sure nobody else is using port 8118

 

image.thumb.png.0dff1aff6a678bfbf165d93cb7dc7ac1.png

 

I'll troubleshoot and see what my findings are. Maybe is time to get a fresh template from the CA? I've had this running since day one, and now most of the settings are persistent. 

Link to comment
  • 2 months later...

I use your Transmission_VPN docker package, and it's been terrific.

But for the past few months, I find I need to restart the docker about once per day.  It isn't crashing, but after a few hours all the transfers just seem to stall.  It'll add new torrents just fine, and they'll populate Seeders and Leechers, but it just won't start downloading or uploading anything. Nothing downloads, and none of my seeds upload anymore. Restarting the container fixes the issue, and it's good for several hours but then stalls again. 

 

Maybe this is some sort of Private Internet Access problem, but does anybody else have this behavior?  I think I might switch PIA servers and see if that makes any difference. (But I think I might've tried that already several weeks ago.)

Edit: 36 hours later -- changing PIA servers didn't help.  But I'm just using the User Scripts plugin to restart the docker every few hours and that's good enough, I suppose.

Edited by AeroMaestro
Link to comment
  • 2 weeks later...

Trying to setup transmission. I added my PIA info but the web UI doesnt seem to start. Other then he IPV6 errors (only running v4 locally) I'm not seeing anything else in the log. Help?! :). I didn't make any setup changes other then adding credentials (which work).

text  error  warn  system  array  login  

2023-09-03 20:31:13 VERIFY EKU OK
2023-09-03 20:31:13 VERIFY OK: depth=0, C=US, ST=CA, L=LosAngeles, O=Private Internet Access, OU=Private Internet Access, CN=zurich405, name=zurich405
2023-09-03 20:31:14 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA512
2023-09-03 20:31:14 [zurich405] Peer Connection Initiated with [AF_INET]212.102.36.20:502
2023-09-03 20:31:14 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.19.111.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.19.111.22 255.255.255.0,peer-id 0,cipher AES-128-GCM'
2023-09-03 20:31:14 OPTIONS IMPORT: timers and/or timeouts modified
2023-09-03 20:31:14 OPTIONS IMPORT: compression parms modified
2023-09-03 20:31:14 OPTIONS IMPORT: --ifconfig/up options modified
2023-09-03 20:31:14 OPTIONS IMPORT: route options modified
2023-09-03 20:31:14 OPTIONS IMPORT: route-related options modified
2023-09-03 20:31:14 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2023-09-03 20:31:14 OPTIONS IMPORT: peer-id set
2023-09-03 20:31:14 OPTIONS IMPORT: adjusting link_mtu to 1627
2023-09-03 20:31:14 OPTIONS IMPORT: data channel crypto options modified
2023-09-03 20:31:14 Data Channel: using negotiated cipher 'AES-128-GCM'
2023-09-03 20:31:14 Outgoing Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
2023-09-03 20:31:14 Incoming Data Channel: Cipher 'AES-128-GCM' initialized with 128 bit key
2023-09-03 20:31:14 net_route_v4_best_gw query: dst 0.0.0.0
2023-09-03 20:31:14 net_route_v4_best_gw result: via 172.17.0.1 dev eth0
2023-09-03 20:31:14 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
2023-09-03 20:31:14 GDG6: remote_host_ipv6=n/a
2023-09-03 20:31:14 net_route_v6_best_gw query: dst ::
2023-09-03 20:31:14 sitnl_send: rtnl: generic error (-101): Network is unreachable
2023-09-03 20:31:14 ROUTE6: default_gateway=UNDEF
2023-09-03 20:31:14 TUN/TAP device tun0 opened
2023-09-03 20:31:14 net_iface_mtu_set: mtu 1500 for tun0
2023-09-03 20:31:14 net_iface_up: set tun0 up
2023-09-03 20:31:14 net_addr_v4_add: 10.19.111.22/24 dev tun0
2023-09-03 20:31:14 net_route_v4_add: 212.102.36.20/32 via 172.17.0.1 dev [NULL] table 0 metric -1
2023-09-03 20:31:14 net_route_v4_add: 0.0.0.0/1 via 10.19.111.1 dev [NULL] table 0 metric -1
2023-09-03 20:31:14 net_route_v4_add: 128.0.0.0/1 via 10.19.111.1 dev [NULL] table 0 metric -1
2023-09-03 20:31:14 WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.
2023-09-03 20:31:14 add_route_ipv6(2000::/3 -> :: metric -1) dev tun0
2023-09-03 20:31:14 net_route_v6_add: 2000::/3 via :: dev tun0 table 0 metric -1
2023-09-03 20:31:14 sitnl_send: rtnl: generic error (-13): Permission denied
2023-09-03 20:31:14 ERROR: Linux IPv6 route can't be added
Up script executed with device=tun0 ifconfig_local=10.19.111.22
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.19.111.22
Using Transmission Web Control UI, overriding TRANSMISSION_WEB_HOME
Enforcing ownership on transmission directories
Applying permissions to transmission directories

-------------------------------------
Transmission will run as
-------------------------------------
User name:   abc
User uid:    99
User gid:    100
-------------------------------------

Updating Transmission settings.json with values from env variables
Attempting to use existing settings.json for Transmission
Could not read existing settings.json. Generating settings.json for Transmission from environment and defaults /etc/transmission/default-settings.json
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.19.111.22
Overriding cache-size-mb because TRANSMISSION_CACHE_SIZE_MB is set to 10
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /downloads
Overriding download-queue-size because TRANSMISSION_DOWNLOAD_QUEUE_SIZE is set to 15
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /downloads/incomplete
Overriding ratio-limit-enabled because TRANSMISSION_RATIO_LIMIT_ENABLED is set to true
Overriding rpc-authentication-required because TRANSMISSION_RPC_AUTHENTICATION_REQUIRED is set to true
Overriding rpc-password because TRANSMISSION_RPC_PASSWORD is set to [REDACTED]
Overriding rpc-port because TRANSMISSION_RPC_PORT is set to 9091
Overriding rpc-username because TRANSMISSION_RPC_USERNAME is set to TRANS_USER
Overriding watch-dir because TRANSMISSION_WATCH_DIR is set to /data/watch
sed'ing True to true
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.
2023-09-03 20:31:14 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2023-09-03 20:31:14 Initialization Sequence Completed
Running functions for token based port fowarding
Reserved Port: 40516  Sun Sep  3 20:31:23 PDT 2023
transmission auth required
waiting for transmission to become responsive
transmission became responsive
    ID   Done       Have  ETA           Up    Down  Ratio  Status       Name
Sum:                None               0.0     0.0
setting transmission port to 40516
localhost:9091/transmission/rpc/ responded: success
Checking port...
Port is open: Yes
#######################
        SUCCESS        
#######################
Port: 40516
Expiration Sun Nov  5 07:31:22 PST 2023
#######################
Entering infinite while loop
Every 15 minutes, check port status
 

Link to comment

EDIT -- I rolled my Transmission_VPN back to version 5.1.0 from about a week ago, and it's working fine.  So the latest update, pushed out this morning, seems to be causing the trouble with IPv6.

 

I'm also having trouble with the Transmission_VPN container, which started for me immediately after updating Unraid to 6.12.4. (Although I also updated my Transmission_VPN Docker container about 1 minute before updating Unraid, and the new issue could be caused by the container update rather than the OS.)


The container appears to startup OK, but the GUI is unresponsive, and the Transmission API isn't responding to any of my *arrs. After about 9 minutes it just gives an "unhealthy" label in the Docker settings. I've checked the log, and here's what I'm seeing (starting with just the first error code):

 

2023-09-05 13:18:59 sitnl_send: rtnl: generic error (-101): Network is unreachable
2023-09-05 13:18:59 ROUTE6: default_gateway=UNDEF
2023-09-05 13:18:59 TUN/TAP device tun0 opened
2023-09-05 13:18:59 net_iface_mtu_set: mtu 1500 for tun0
2023-09-05 13:18:59 net_iface_up: set tun0 up
2023-09-05 13:18:59 net_addr_v4_add: 10.13.111.7/24 dev tun0
2023-09-05 13:18:59 net_route_v4_add: 181.215.182.203/32 via 172.17.0.1 dev [NULL] table 0 metric -1
2023-09-05 13:18:59 net_route_v4_add: 0.0.0.0/1 via 10.13.111.1 dev [NULL] table 0 metric -1
2023-09-05 13:18:59 net_route_v4_add: 128.0.0.0/1 via 10.13.111.1 dev [NULL] table 0 metric -1
2023-09-05 13:18:59 WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for tun0, therefore the route installation may fail or may not work as expected.
2023-09-05 13:18:59 add_route_ipv6(2000::/3 -> :: metric -1) dev tun0
2023-09-05 13:18:59 net_route_v6_add: 2000::/3 via :: dev tun0 table 0 metric -1
2023-09-05 13:18:59 sitnl_send: rtnl: generic error (-13): Permission denied
2023-09-05 13:18:59 ERROR: Linux IPv6 route can't be added
2023-09-05 13:18:59 WARNING: External program may not be called unless '--script-security 2' or higher is enabled. See --help text or man page for detailed info.
2023-09-05 13:18:59 WARNING: Failed running command (--route-up): disallowed by script-security setting
2023-09-05 13:18:59 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2023-09-05 13:18:59 Initialization Sequence Completed

 

So it looks like there's something involving IPv6 that it doesn't like, but I don't see any IPv6 settings anywhere in the Transmission_VPN settings.  Perhaps this is something about the Private Internet Access servers that Unraid doesn't like anymore?

Edited by AeroMaestro
Link to comment

You can revert back to a previous version, you just have to set the tag to the version you want. I am running the :dev tag and it seems to be running ok. IPV6 errors have been consistant in my logs for almost as long as I have been running this. I do have unraid set to IPV4 only.

 

. I have only created the template, not the docker. looks like there was an update within the last couple days

 

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

Edited by clowrym
Link to comment
  • 4 weeks later...
  • 2 months later...
  • 1 month later...

I've installed the latest version of the Transmission_VPN Docker container.  It's working and I can use the GUI to get into it.  When I try starting torrent downloads, the number of seeds, leechers and says it's downloading.  Only problem is it doesn't download anything.  I've got PIA configured properly; I could see it in the logs from the container.  Is there something messed up with this container?

Link to comment
12 hours ago, awshirley said:

I've installed the latest version of the Transmission_VPN Docker container.  It's working and I can use the GUI to get into it.  When I try starting torrent downloads, the number of seeds, leechers and says it's downloading.  Only problem is it doesn't download anything.  I've got PIA configured properly; I could see it in the logs from the container.  Is there something messed up with this container?

Aloha,
does your Dowmload have Leechers and Seeders? What does the Status for the Downloads say? Just "Downloading" or something else?

Link to comment
  • 2 months later...

Looking for support with TransmissionBT +OPENVPN

I am using ProtonVPN as my VPN provider - everything connects successfully and TransmissionBT works but the port assigned by the script is NOT open according to TransmissionBT or if I find the IP and check on yougetsignal.com. According to the logs:
STARTING TRANSMISSION
Provider PROTONVPN 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.
2024-03-19 19:31:38 Initialization Sequence Completed
 and it shows a box with ProtonVPN Port Forwarding in blue. 

 

How do I TS this and get the port forwarding working?
image.thumb.png.90dae8354c9b3b3e98dbf60b68d418e0.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.