[Support] Clowrym's Docker Repository


clowrym

Recommended Posts

On 10/30/2020 at 11:38 PM, Mechman293homelab said:

Thanks for the work around. I too am having the "Connection Refused" issue on the latest update.

Do you happen to be using a custom docker network (e.g. custom : proxynet), like with LetsEncrypt instead of the default "bridge"? This is the reason why the network does not come up properly with 3.0. I have tinkered around with this some more and choosing Network type = Bridge allows the docker to start-up correctly with a network.

 

I don't have a solution to this if I want the Docker to be on the correct network for external access...

Link to comment
On 10/30/2020 at 10:40 AM, clowrym said:

interessting, I'm having no issues with the latest....not sure what is different with your set up compared to mine.....

Network type with what used to work (custom docker network - per Spaceinvader One video - Reverse proxy with LetsEncrypt) using "docker network create <name of network>" and choosing that as specific network causes the Docker to fail to bind a listening port on the correct network. I fiddled around with it until I tried "Bridge" as the network type for the docker and then it came up. So I am staying with 2.14 until a solution becomes obvious.

Link to comment
2 hours ago, LTM said:

Just putting the Github issue here. More active than these forums.

https://github.com/haugene/docker-transmission-openvpn/issues/1463

 

Some people have had success changing the PIA login details to the ones you use to log in (p#######) instead of the 'PPTP/L2TP/SOCKS' username and password (x#######). It took like an hour, but this eventually did the trick for me.

that could be why i've never had these issues. I've always used my PIA login details....

Link to comment

On Transmission_VPN, I've switched to using NordVPN instead of PIA.  I've got Nord working using the provider specific variables.  Part of getting Nord to work for me was deleting the OPENVPN_CONFIG variable.  However if I restart the docker container, OPENVPN_CONFIG is automatically created again and points to a PIA config, causing the docker to not start properly because it can't connect.  If I manually remove the variable again and then restart the container it works, but the OPENVPN_CONFIG variable will always come back on subsequent restarts.  How can I make it so OPENVPN_CONFIG does not keep coming back?

 

Thanks

Link to comment

Am I the only one having issues with downloading torrents pushed from Sonarr, Radarr. Looks like the PIA is literally blocking the trackers. I'm using Switzerland, but I've changed to so many different ones. 

 

I just got off with the chat and they said that for now they only support proxy-nl.privateinternetaccess.com 1080 for torrenting. I'm assuming is this setting from the website. https://www.vpnuniversity.com/tutorial/pia-socks-proxy 

 

Can someone confirm if that's the setting everyone is using right now?

Edited by gacpac
Link to comment
alot of these issues could be related to the release of V3, I would post the issues on github. I'll also have to have a look at the template, and see if there are some changes I need to make .
 
Haugene's Issues on Github
Thanks man, I've been checking and I don't think it's you. Looks like the trackers are blacklisted or something. I ended up adding a big list of trackers to the torrents and got them started.

Found a github that updates trackers and uses an sh to add that into each of the torrents sounds pretty nice but I don't know how to include that into the image or just point transmission to that.

https://github.com/ngosang/trackerslist

Sent from my Pixel 2 XL using Tapatalk

Link to comment
5 minutes ago, gacpac said:

Thanks man, I've been checking and I don't think it's you. Looks like the trackers are blacklisted or something. I ended up adding a big list of trackers to the torrents and got them started.

Found a github that updates trackers and uses an sh to add that into each of the torrents sounds pretty nice but I don't know how to include that into the image or just point transmission to that.

https://github.com/ngosang/trackerslist

Sent from my Pixel 2 XL using Tapatalk
 

I just set up a second docker on my test server for the dev channel, and it seems to be working using switzerland....or at least for the last hour or so..... I'll play around this weekend and see if i can update the template to be a little more suited to V3, i notice there are a few changes, so there are a few variables that i can remove now.

 

I also see an issue listed for "special charracters" in the PIA password which isn't working atm.

 

I also see in the release notes there is, or is going to be a wway to add user scripts in the future, may make adding the update tracker github you posted above. 

Edited by clowrym
Link to comment
I just set up a second docker on my test server for the dev channel, and it seems to be working using switzerland....or at least for the last hour or so..... I'll play around this weekend and see if i can update the template to be a little more suited to V3, i notice there are a few changes, so there are a few variables that i can remove now.
 
I also see an issue listed for "special charracters" in the PIA password which isn't working atm.
 
I also see in the release notes there is, or is going to be a wway to add user scripts in the future, may make adding the update tracker github you posted above. 
Oh man you the best. I know that for now that's my lucky ticket. Because when I download anime that uses trackers from nyaa.si no issues. I noticed that only when I get movies or shows that use rarbg and Cooper that never download. I wouldn't mind sending you by private the magnet files, maybe you can replicate.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
Link to comment

I am new to Unraid and trying to figure out this plugin I keep getting this error no mater witch option for guidance I pick

 

403: Forbidden

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.

If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

 


Mon Nov 16 01:23:44 2020 SIGTERM[hard,] received, process exiting
Starting container with revision: 93d0141d928ec661411e2c6f0e079aeff2c018dd
mknod: /dev/net/tun: File exists
Using OpenVPN provider: PIA
Provider PIA has a custom startup script, executing it
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.lHmhpe
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
Modify configs for this container
Starting OpenVPN using config default.ovpn
Setting OpenVPN credentials...
adding route to local network 10.1.1.0/24 via 172.17.0.1 dev eth0
Mon Nov 16 01:24:17 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Mon Nov 16 01:24:17 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Mon Nov 16 01:24:17 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Nov 16 01:24:17 2020 CRL: loaded 1 CRLs from file [[INLINE]]
Mon Nov 16 01:24:17 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:17 2020 UDP link local: (not bound)
Mon Nov 16 01:24:17 2020 UDP link remote: [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:17 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Nov 16 01:24:18 2020 [buenosaires401] Peer Connection Initiated with [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:19 2020 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
Mon Nov 16 01:24:19 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3
Mon Nov 16 01:24:19 2020 TUN/TAP device tun0 opened
Mon Nov 16 01:24:19 2020 /sbin/ip link set dev tun0 up mtu 1500
Mon Nov 16 01:24:19 2020 /sbin/ip addr add dev tun0 10.1.112.16/24 broadcast 10.1.112.255
Mon Nov 16 01:24:19 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.1.112.16 255.255.255.0 init
Up script executed with tun0 1500 1553 10.1.112.16 255.255.255.0 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.1.112.16
Using Transmission Web Control UI, overriding TRANSMISSION_WEB_HOME
Updating Transmission settings.json with values from env variables
Using existing settings.json for Transmission /data/transmission-home/settings.json
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.1.112.16
Overriding cache-size-mb because TRANSMISSION_CACHE_SIZE_MB is set to 10
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /download
Overriding download-queue-size because TRANSMISSION_DOWNLOAD_QUEUE_SIZE is set to 15
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /download/incomplete
Could not coerce TRANSMISSION_RATIO_LIMIT value 1.1 to expected type <class 'int'>
Traceback (most recent call last):
File "/etc/transmission/updateSettings.py", line 69, in <module>
env_value = setting_type(env_value)
ValueError: invalid literal for int() with base 10: '1.1'
sed'ing True to true
Enforcing ownership on transmission config directories
Applying permissions to transmission config directories

-------------------------------------
Transmission will run as
-------------------------------------
User name: abc
User uid: 99
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=yes
Transmission startup script complete.
Mon Nov 16 01:24:19 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.
Mon Nov 16 01:24:19 2020 Initialization Sequence Completed



yes: Broken pipe
port is 33721
port is 33721
the port has been bound to 33721 Mon Nov 16 01:24:28 PST 2020
transmission auth not 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 33721
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Port is open: Yes

initial setup complete!

waiting for rebind loop.................

Link to comment
6 hours ago, bradywang said:

I am new to Unraid and trying to figure out this plugin I keep getting this error no mater witch option for guidance I pick

 

403: Forbidden

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.

If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

 


Mon Nov 16 01:23:44 2020 SIGTERM[hard,] received, process exiting
Starting container with revision: 93d0141d928ec661411e2c6f0e079aeff2c018dd
mknod: /dev/net/tun: File exists
Using OpenVPN provider: PIA
Provider PIA has a custom startup script, executing it
Downloading OpenVPN config bundle openvpn-nextgen into temporary file /tmp/tmp.lHmhpe
Extract OpenVPN config bundle into PIA directory /etc/openvpn/pia
Modify configs for this container
Starting OpenVPN using config default.ovpn
Setting OpenVPN credentials...
adding route to local network 10.1.1.0/24 via 172.17.0.1 dev eth0
Mon Nov 16 01:24:17 2020 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Mon Nov 16 01:24:17 2020 library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Mon Nov 16 01:24:17 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Mon Nov 16 01:24:17 2020 CRL: loaded 1 CRLs from file [[INLINE]]
Mon Nov 16 01:24:17 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:17 2020 UDP link local: (not bound)
Mon Nov 16 01:24:17 2020 UDP link remote: [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:17 2020 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Mon Nov 16 01:24:18 2020 [buenosaires401] Peer Connection Initiated with [AF_INET]190.106.134.82:1198
Mon Nov 16 01:24:19 2020 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
Mon Nov 16 01:24:19 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/3
Mon Nov 16 01:24:19 2020 TUN/TAP device tun0 opened
Mon Nov 16 01:24:19 2020 /sbin/ip link set dev tun0 up mtu 1500
Mon Nov 16 01:24:19 2020 /sbin/ip addr add dev tun0 10.1.112.16/24 broadcast 10.1.112.255
Mon Nov 16 01:24:19 2020 /etc/openvpn/tunnelUp.sh tun0 1500 1553 10.1.112.16 255.255.255.0 init
Up script executed with tun0 1500 1553 10.1.112.16 255.255.255.0 init
Updating TRANSMISSION_BIND_ADDRESS_IPV4 to the ip of tun0 : 10.1.112.16
Using Transmission Web Control UI, overriding TRANSMISSION_WEB_HOME
Updating Transmission settings.json with values from env variables
Using existing settings.json for Transmission /data/transmission-home/settings.json
Overriding bind-address-ipv4 because TRANSMISSION_BIND_ADDRESS_IPV4 is set to 10.1.112.16
Overriding cache-size-mb because TRANSMISSION_CACHE_SIZE_MB is set to 10
Overriding download-dir because TRANSMISSION_DOWNLOAD_DIR is set to /download
Overriding download-queue-size because TRANSMISSION_DOWNLOAD_QUEUE_SIZE is set to 15
Overriding incomplete-dir because TRANSMISSION_INCOMPLETE_DIR is set to /download/incomplete
Could not coerce TRANSMISSION_RATIO_LIMIT value 1.1 to expected type <class 'int'>
Traceback (most recent call last):
File "/etc/transmission/updateSettings.py", line 69, in <module>
env_value = setting_type(env_value)
ValueError: invalid literal for int() with base 10: '1.1'
sed'ing True to true
Enforcing ownership on transmission config directories
Applying permissions to transmission config directories

-------------------------------------
Transmission will run as
-------------------------------------
User name: abc
User uid: 99
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=yes
Transmission startup script complete.
Mon Nov 16 01:24:19 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.
Mon Nov 16 01:24:19 2020 Initialization Sequence Completed



yes: Broken pipe
port is 33721
port is 33721
the port has been bound to 33721 Mon Nov 16 01:24:28 PST 2020
transmission auth not 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 33721
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Port is open: Yes

initial setup complete!

waiting for rebind loop.................

Lol that one is easy though. 

Add your IP space in here 

image.thumb.png.48fc8365912311dc273b78b1f102de8a.png

 

My house uses 172.16.1.0/24 however, my unraid dockers use 172.17, 172.18 and like that so. I added 172.16.0.0/16 for the bigger scope.

If you are using 10.0.0.0/24 then do the same as me

Link to comment

FYI People that are having issues with the recent upgrade to V3 a lot of people are having issues with the trackers not connecting. Meaning your torrents won't download. 

 

The solution found and at least what has worked for me.

- Copy your torrent magnet links to a notepad

- Make note of any custom setting you have "blacklist, maximun seed time, etc" 

- Turn off the docker

- Rename your transmission-home folder to transmission-home.old 

- Restart the container and let the folder recreate itself

 

Most of the steps are optional, you can turn of the docker and delete the folder if you don't have custom settings like me :) 

 

You can follow the github problem here 

https://github.com/haugene/docker-transmission-openvpn/issues/1507

Edited by gacpac
Link to comment
2 hours ago, gacpac said:

Lol that one is easy though. 

Add your IP space in here 

image.thumb.png.48fc8365912311dc273b78b1f102de8a.png

 

My house uses 172.16.1.0/24 however, my unraid dockers use 172.17, 172.18 and like that so. I added 172.16.0.0/16 for the bigger scope.

If you are using 10.0.0.0/24 then do the same as me

You need to change rpc-whitelist-enabled to false in the transmission settings.json file. I believe it's on by default

Link to comment
On 11/12/2020 at 2:42 PM, Arbadacarba said:

Not having seen mass complaints on here I have to believe something has gone wrong with my install... But just in case I missed something.

 

For the past couple of weeks thing have not been working... If I try to use Switzerland the UI doesn't load and if I use Denmark, it loads but nothing downloads...

 

 

So, after struggling with this for over a week, I told the system to check for updates and discovered there was one... Now it's working.. Sheesh... I could have found that earlier.

Link to comment
8 hours ago, clowrym said:

You need to change rpc-whitelist-enabled to false in the transmission settings.json file. I believe it's on by default

The only files i see in the /mnt/user/appdata/Transmission_VPN are 2 files that contain only 2 lines witch are username and password

 

and i have set the local_network to 10.1.1.0/24 any other setting and it wont start

Link to comment
38 minutes ago, bradywang said:

The only files i see in the /mnt/user/appdata/Transmission_VPN are 2 files that contain only 2 lines witch are username and password

 

and i have set the local_network to 10.1.1.0/24 any other setting and it wont start

Let me help you a little bit. Currently there's a bug with the transmission ratio. You have to modify that manually in the settings.json file or don't it's okay as long as you don't use it in the template. And you don't see the data because is somewhere else not in config.

 

I'm attaching picture from a previous post that might help you go the right path, and my custom variables are optional. 

 

 

Link to comment
1 hour ago, bradywang said:

The only files i see in the /mnt/user/appdata/Transmission_VPN are 2 files that contain only 2 lines witch are username and password

 

and i have set the local_network to 10.1.1.0/24 any other setting and it wont start

the settings.json file is in whatever location you set for image.thumb.png.5d8895f68b60880ac789310714aa359c.png:

in my case its located at /mnt/user/T_Media/Torrent/transmission-home, and should look similar to this:image.png.cdcbe944838442859d7cff9e65e89033.png

 

Link to comment

So some recent PIA changes have broken the Transmission_VPN docker when using PIA. There are ways to work around it.

  1. PIA changed the name of the Zips that the new versions of the Docker download to get all the various servers you can connect to. The way around this is to add a variable named "PIA_OPENVPN_CONFIG_BUNDLE" and then set the value to "openvpn", there are several other valid values, but I'd recommend going to haugene's github and look up the configure shell script for PIA to find the other ones.
  2. The other issue is PIA changed how the OpenVPN files in their bundles are named. Now they are all lower case and have underscores instead of spaces, i.e. "CA Toronto" is now "ca_toronto". So your "OPENVPN_CONFIG" needs to conform to the new naming scheme.

That is it to work around PIA's recent changes. The first step, hopefully won't be necessary "soon". I have submitted an issue for it on the GitHub for the docker. The second however will need to be addressed in the Unraid template to correct the available values for that variable. My work around requires you to swap to Advanced mode in the Edit screen and edit the available values to the way the files are now named, otherwise Unraid just sets your value to blank if it isn't in the "Default Value" section for the variable (no clue why it would just throw away my manual setting like that but it is something I've encountered several times).

 

I do have another issue, and it is tied to the recent 3.0 version of the docker. For whatever reason if the "TRANSMISSION_RATIO_LIMIT" or "TRANSMISSION_RATIO_LIMIT_ENABLED" are even included, even if the "ENABLED" one is set to false, the docker reports the port that PIA returns as closed, and consequently, like a lot of you have seen, prevents Transmission from connecting to basically any tracker, at least that has been my experience. Removing those variables outright gets it working just fine, however every time there is an update for the docker those variables get added back in Unraid and I have to go in and manually deleted them. I've turned off my auto update for that particular docker and just do it manually when I see there is an update. I believe most of the Transmission settings are supposed to be persistent now with the release of v3.0, so it might be possible to just remove the vast majority of the Transmission configuration options as Environment variables.

Link to comment
9 hours ago, pokeguru87 said:

So some recent PIA changes have broken the Transmission_VPN docker when using PIA. There are ways to work around it.

  1. PIA changed the name of the Zips that the new versions of the Docker download to get all the various servers you can connect to. The way around this is to add a variable named "PIA_OPENVPN_CONFIG_BUNDLE" and then set the value to "openvpn", there are several other valid values, but I'd recommend going to haugene's github and look up the configure shell script for PIA to find the other ones.
  2. The other issue is PIA changed how the OpenVPN files in their bundles are named. Now they are all lower case and have underscores instead of spaces, i.e. "CA Toronto" is now "ca_toronto". So your "OPENVPN_CONFIG" needs to conform to the new naming scheme.

That is it to work around PIA's recent changes. The first step, hopefully won't be necessary "soon". I have submitted an issue for it on the GitHub for the docker. The second however will need to be addressed in the Unraid template to correct the available values for that variable. My work around requires you to swap to Advanced mode in the Edit screen and edit the available values to the way the files are now named, otherwise Unraid just sets your value to blank if it isn't in the "Default Value" section for the variable (no clue why it would just throw away my manual setting like that but it is something I've encountered several times).

 

I do have another issue, and it is tied to the recent 3.0 version of the docker. For whatever reason if the "TRANSMISSION_RATIO_LIMIT" or "TRANSMISSION_RATIO_LIMIT_ENABLED" are even included, even if the "ENABLED" one is set to false, the docker reports the port that PIA returns as closed, and consequently, like a lot of you have seen, prevents Transmission from connecting to basically any tracker, at least that has been my experience. Removing those variables outright gets it working just fine, however every time there is an update for the docker those variables get added back in Unraid and I have to go in and manually deleted them. I've turned off my auto update for that particular docker and just do it manually when I see there is an update. I believe most of the Transmission settings are supposed to be persistent now with the release of v3.0, so it might be possible to just remove the vast majority of the Transmission configuration options as Environment variables.

I've been testing a new template for the docker on V3, but it hasnt been very stable up to this point. Hopefully be able to do an update this weekend on the transmission template.

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.