[Support] Clowrym's Docker Repository


clowrym

Recommended Posts

  • 3 weeks later...

I'm getting some problems with the Transmission VPN. currently I have it with PIA and it works fine. But I cannot get the docker openvpn-as to access the transmission remotely. 

 

I noticed that If I turn off the transmission the vpn connects right away. And if I connect remotely and then start the transmission it works. 

 

I even added this. 

 

image.thumb.png.eddfdec1b62c3328bd85eb26f1a759e0.png

 

Also I remember this wasn't like this before. Because I used PIA before. 

 

Link to comment

Sorry for the late reply.. its been a busy couple weeks at work!! 

 

There seems to be an issue with adding multiple local networks in the cell you have above, I tried the same originally when I first made this template. I ended up adding a script to user scripts plugin that runs on server boot & that I run if I force a restart/update on Transmission. I have listed it below.... I know its a work around, but I havent figured out how to allow multiple networks in the docker template.....

 

I use the script below for access loutside of my local network thru the VPN I have set up for my work computer / phone when I am not on ly local network.

 

adjust the ip addresses to suit your network setup!!

#!/bin/bash
echo adding 10.1.0.0/25 LAN_NETWORK
docker exec Transmission_VPN /bin/sh -c "/sbin/ip r a 10.1.0.0/24 via 172.17.0.1 dev eth0"
echo Netowrk added
exit

 

Edited by clowrym
Link to comment
On 12/4/2018 at 1:04 AM, clowrym said:

Sorry for the late reply.. its been a busy couple weeks at work!! 

 

There seems to be an issue with adding multiple local networks in the cell you have above, I tried the same originally when I first made this template. I ended up adding a script to user scripts plugin that runs on server boot & that I run if I force a restart/update on Transmission. I have listed it below.... I know its a work around, but I havent figured out how to allow multiple networks in the docker template.....

 

I use the script below for access loutside of my local network thru the VPN I have set up for my work computer / phone when I am not on ly local network.

 

adjust the ip addresses to suit your network setup!!


#!/bin/bash
echo adding 10.1.0.0/25 LAN_NETWORK
docker exec Transmission_VPN /bin/sh -c "/sbin/ip r a 10.1.0.0/24 via 172.17.0.1 dev eth0"
echo Netowrk added
exit

 

@clowrym Thanks for that. Actually, I was able to make it see my other networks. To me still doesn't make sense because I keep using the server IP plus the port but. 

 

image.thumb.png.e15fbbf929802ad6ff1c7aa9da01e03e.png

 

I had to add manually there the virtual network and the vpn network to access the torrent.

 

Now Something that really bugs my mind and I don't know why is. 

 

Currently I have the OpenVPN-as docker container setup with UDP using port 9443, forwarded through my router. Works perfect. But when I have the Transmission docker running, My OpenVPN doesn't connect using UDP. I currently have it running on TCP. 

 

If Transmission for PIA is using OpenVPN Port 1198, why is it blocking my connection for my own VPN. 

 

Link to comment
  • 4 weeks later...

I've just installed transmission-openvpn docker and got it running with NordVPN. I do not recommend anyone to use NordVPN as they do not support port forwarding so my speeds are abysmal. They are refusing to issue me with a refund for the unused subscription time as I no longer need Nord.

 

Anyway, onto why I'm here.. I've noticed two plain text files in this config folder containing the credentials for Transmission and the credentials for my NordVPN account. They are named:

openvpn-credentials.txt

transmission-credentials.txt

 

This seems like a pretty serious security vulnerability? Password should never be stored in plain text... 🤨

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

I've just installed transmission-openvpn docker and got it running with NordVPN. I do not recommend anyone to use NordVPN as they do not support port forwarding so my speeds are abysmal. They are refusing to issue me with a refund for the unused subscription time as I no longer need Nord.

 

Anyway, onto why I'm here.. I've noticed two plain text files in this config folder containing the credentials for Transmission and the credentials for my NordVPN account. They are named:

openvpn-credentials.txt

transmission-credentials.txt

 

This seems like a pretty serious security vulnerability? Password should never be stored in plain text... 🤨

 

 

Interesting, not sure why those are there, my password is stored in the config file for transmission

 

I didnt create the docker, only the template for unraid, you could post here: https://github.com/haugene/docker-transmission-openvpn

Link to comment

Yeah that repo writes the credentials out to a plain text file in start.sh for openvpn:

# add OpenVPN user/pass
if [[ "${OPENVPN_USERNAME}" == "**None**" ]] || [[ "${OPENVPN_PASSWORD}" == "**None**" ]] ; then
  if [[ ! -f /config/openvpn-credentials.txt ]] ; then
    echo "OpenVPN credentials not set. Exiting."
    exit 1
  fi
  echo "Found existing OPENVPN credentials..."
else
  echo "Setting OPENVPN credentials..."
  mkdir -p /config
  echo "${OPENVPN_USERNAME}" > /config/openvpn-credentials.txt
  echo "${OPENVPN_PASSWORD}" >> /config/openvpn-credentials.txt
  chmod 600 /config/openvpn-credentials.txt
fi

I have no idea why though. It doesn't seem to get referenced again after that *.txt is initially created. Baffling!

Link to comment
13 hours ago, danger781 said:

I've just installed transmission-openvpn docker and got it running with NordVPN. I do not recommend anyone to use NordVPN as they do not support port forwarding so my speeds are abysmal. They are refusing to issue me with a refund for the unused subscription time as I no longer need Nord.

 

I've not run into this problem. I get incoming connections from peers just fine. At the same time, I've also verified all traffic is being tunneled through NordVPN (they only see my VPN IP).

 

13 hours ago, danger781 said:

Anyway, onto why I'm here.. I've noticed two plain text files in this config folder containing the credentials for Transmission and the credentials for my NordVPN account. They are named:

openvpn-credentials.txt

transmission-credentials.txt

 

This seems like a pretty serious security vulnerability? Password should never be stored in plain text... 🤨

 

Due to the nature of how these programs work, how else would you store them? The applications must know what the passwords are to submit the services you're subscribed to. If you encrypt it, the application has no method to extract it to submit the credential to the service on every startup of the container. Best thing to do is to make sure such files are only readable for the application that needs it.

 

 

Link to comment
  • 1 month later...

Hi all,

 

I'm having trouble getting the Transmission docker up and running. The log shows the following error:


Got new port 59595 from PIA
transmission auth required
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Error: portTested: http error 0: No Response

 

Reading through the thread it looks to be the same DNS issue reported on P.2. It's probably very simple but I don't know how to add the DNS flag, any pointers would be appreciated.

 

On 1/2/2018 at 6:55 PM, clowrym said:

 

Looks like a DNS problem, Can you add dns flag to your template --dns 8.8.8.8

Thanks!

Edited by Hendricks
Link to comment
6 hours ago, Hendricks said:

Hi all,

 

I'm having trouble getting the Transmission docker up and running. The log shows the following error:


Got new port 59595 from PIA
transmission auth required
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Error: portTested: http error 0: No Response

 

Reading through the thread it looks to be the same DNS issue reported on P.2. It's probably very simple but I don't know how to add the DNS flag, any pointers would be appreciated.

 

Thanks!

make sure "advanced view" is on for your docker template and  add --dns 8.8.8.8 to the extra parameters 

Link to comment

Thanks Clowrym, i thought it had to be something fairly simple. The log now shows that the port is open, however the GUI doesn't come up...any thoughts?

 

STARTING TRANSMISSION
CONFIGURING PORT FORWARDING
Transmission startup script complete.
Wait for tunnel to be fully initialized and PIA is ready to give us a port
Fri Feb 8 17:29:13 2019 Initialization Sequence Completed
Generating new client id for PIA
Got new port 21613 from PIA
transmission auth required
localhost:9091/transmission/rpc/ responded: "success"
Checking port...
Port is open: Yes

Link to comment
DId you add your local network properly? ie. 192.168.1.0/24 or whatever local network your using? Also, are you trying to access it from within your network? If not then you have to add whatever network's you want to access it from.
This is exactly the problem you are getting. Remember the containers run in a virtual network, if you cinnect via VPN or whatever network. You have to add it to the options for the container as well.

Sent from my Pixel 2 XL using Tapatalk

Link to comment
  • 2 weeks later...

I am having trouble getting my NordVPN to work with Transmission_VPN.  When I try to access the WebUI I get an error of "This site can't be reached"

Any ideas?

Here is what my log looks like...

 

Using OpenVPN provider: NORDVPN
Starting OpenVPN using config default.ovpn
Setting OPENVPN credentials...
adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0
Fri Feb 22 00:38:41 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Fri Feb 22 00:38:41 2019 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08
Fri Feb 22 00:38:41 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Feb 22 00:38:41 2019 NOTE: --fast-io is disabled since we are not using UDP
Fri Feb 22 00:38:41 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Feb 22 00:38:41 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Feb 22 00:38:41 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.30.232.17:443
Fri Feb 22 00:38:41 2019 Socket Buffers: R=[87380->87380] S=[65536->65536]
Fri Feb 22 00:38:41 2019 Attempting to establish TCP connection with [AF_INET]185.30.232.17:443 [nonblock]

 

Edited by mgranger
Link to comment
  • 2 weeks later...
23 hours ago, plantsandbinary said:

@clowrym Hey there's way more providers supported by this container in Github than what is available when installing in Unraid: https://github.com/haugene/docker-transmission-openvpn

 

For example. MULLVAD is supported but it's not possible to select it in the TransmissionVPN setup window. It's not in the list. Why is this?

When I set up the template I added all that were available at the time, you can add additional ones at any time here:

 

image.thumb.png.e919d82549d5870581f45ca8e9610fb0.png

When I get some time, I will try and add any new ones to the template.

 

  • Like 1
Link to comment

Hi, I feel kindof dumb because I cannot get the Transmission_VPN installed (had no problem with e.g. a krusader docker). How do I add the template? I added the link to https://github.com/clowrym/docker-templates/blob/master/Transmission_VPN.xml into the docker template repositories but then I cannot use it when adding a docker. It is not shown in the dropdown "Select a template". 

 

Nevermind... I didn't see that I could update the CA-plugin... now I feel even more dumb 😃 

Edited by cen
forgot to update
Link to comment
On 2/21/2019 at 8:19 PM, mgranger said:

yes i am trying to get the webui from a computer that is on 192.168.1.x

Did you ever find a solution? I'm having a similar problem. My log doesn't seem to have a specific error so I'm a little lost.

 

Using OpenVPN provider: PROXPN
Supplied config US Seattle.ovpn could not be found.
Using default OpenVPN gateway for provider proxpn
Setting OPENVPN credentials...
adding route to local network 192.168.1.0/24 via 172.17.0.1 dev eth0
Thu Mar 14 04:35:51 2019 us=492872 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=492939 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=492948 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Thu Mar 14 04:35:51 2019 us=493143 Current Parameter Settings:
Thu Mar 14 04:35:51 2019 us=493159   config = '/etc/openvpn/proxpn/default.ovpn'
Thu Mar 14 04:35:51 2019 us=493169   mode = 0
Thu Mar 14 04:35:51 2019 us=493177   persist_config = DISABLED
Thu Mar 14 04:35:51 2019 us=493184   persist_mode = 1
Thu Mar 14 04:35:51 2019 us=493190 NOTE: --mute triggered...
Thu Mar 14 04:35:51 2019 us=493213 326 variation(s) on previous 5 message(s) suppressed by --mute
Thu Mar 14 04:35:51 2019 us=493221 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Thu Mar 14 04:35:51 2019 us=493235 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 2.08
Thu Mar 14 04:35:51 2019 us=493759 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Thu Mar 14 04:35:51 2019 us=493769 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Mar 14 04:35:51 2019 us=494322 LZO compression initializing
Thu Mar 14 04:35:51 2019 us=494393 Control Channel MTU parms [ L:1622 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Thu Mar 14 04:35:51 2019 us=494436 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ]
Thu Mar 14 04:35:51 2019 us=494464 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 512,key-method 2,tls-client'
Thu Mar 14 04:35:51 2019 us=494471 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize512,key-method 2,tls-server'
Thu Mar 14 04:35:51 2019 us=494481 TCP/UDP: Preserving recently used remote address: [AF_INET]50.7.88.172:443
Thu Mar 14 04:35:51 2019 us=494509 Socket Buffers: R=[212992->212992] S=[212992->212992]
Thu Mar 14 04:35:51 2019 us=494518 UDP link local: (not bound)
Thu Mar 14 04:35:51 2019 us=494525 UDP link remote: [AF_INET]50.7.88.172:443

 

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.