-
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Config usedTrying to install transmission open-VPN on a NAS synologu DS220+ using portainer. I use NORDVPN as a provider Current BehaviorIt seems that it doesn't want to start, don't know why Expected BehaviorLaunching transmission with NORDVPN's VPN active How have you tried to solve the problem?This is my docker compose: Log outputEnvironment- OS: DSM 7.0
- Docker: 20.10.3-1233Anything else?No response |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 7 replies
-
|
Please read the pinned issue regarding DSM. |
Beta Was this translation helpful? Give feedback.
-
|
OK so, I simplified everything, trying not to use the resolv.conf file. Here is my docker-compose: And here are the log: I have the same issue with the DNS, but I didn't touch anything. I really don't get it. I read the pinned issue regarding DNS but it's not the same problem I encounter. |
Beta Was this translation helpful? Give feedback.
-
|
Well, config looks fine but the container doesn’t have a connection at all
it seems. Please look into your docker setup/host.. does it resolve dns
properly? Try another barebones container? Before the tunnel is up it
should be using direct host dns to resolve if you don’t override this.. so
looks more like something not correct with docker
…On Fri, Oct 8, 2021 at 16:10 Grégory Loyer ***@***.***> wrote:
OK so, I simplified everything, trying not to use the resolv.conf file.
Here is my docker-compose:
services:
transmission-openvpn:
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun
volumes:
- /volume1/docker/transmissionVPN:/data
- /volume1/downloads:/data/completed
environment:
- OPENVPN_PROVIDER=NORDVPN
- OPENVPN_USERNAME=***
- OPENVPN_PASSWORD=***
- NORDVPN_COUNTRY=US
- NORDVPN_PROTOCOL=tcp
- NORDVPN_CATEGORY=legacy_p2p
- LOCAL_NETWORK=192.168.1.1/16
- PUID=1026
- PGID=100
logging:
driver: json-file
options:
max-size: 10m
ports:
- 9091:9091
image: haugene/transmission-openvpn
And here are the log:
Starting container with revision: ae45b1f,
WARNING: initial DNS resolution test failed,
Creating TUN device /dev/net/tun,
mknod: /dev/net/tun: File exists,
Using OpenVPN provider: NORDVPN,
Running with VPN_CONFIG_SOURCE auto,
Provider NORDVPN has a bundled setup script. Defaulting to internal config,
Executing setup script for NORDVPN,
2021-10-08 07:02:09 Checking curl installation,
2021-10-08 07:02:09 Removing existing configs,
2021-10-08 07:02:09 Selecting the best server...,
2021-10-08 07:02:09 Searching for technology: openvpn_tcp,
2021-10-08 07:02:09 Unable to find a server with the specified parameters, using any recommended server,
2021-10-08 07:02:09 Best server : ,
2021-10-08 07:02:09 Downloading config: default.ovpn,
2021-10-08 07:02:09 Downloading from: https://downloads.nordcdn.com/configs/files/ovpn_tcp/servers/.tcp.ovpn,
curl: (6) Could not resolve host: downloads.nordcdn.com,
No VPN configuration provided. Using default.,
Modifying /etc/openvpn/nordvpn/default.ovpn for best behaviour in this container,
Modification: Point auth-user-pass option to the username/password file,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
Modification: Change ca certificate path,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
Modification: Change ping options,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
sed: can't read /etc/openvpn/nordvpn/default.ovpn: No such file or directory,
Modification: Update/set resolv-retry to 15 seconds,
Modification: Change tls-crypt keyfile path,
Modification: Set output verbosity to 3,
Modification: Remap SIGUSR1 signal to SIGTERM, avoid OpenVPN restart loop,
Setting OpenVPN credentials...,
adding route to local network 192.168.1.1/16 via 172.22.0.1 dev eth0,
RTNETLINK answers: Invalid argument,
Fri Oct 8 07:02:49 2021 disabling NCP mode (--ncp-disable) because not in P2MP client or server mode,
Options error: You must define TUN/TAP device (--dev),
Use --help for more information.
I have the same issue with the DNS, but I didn't touch anything. I really
don't get it. I read the pinned issue regarding DNS but it's not the same
problem I encounter.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1993 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYUKM4DXUVDCY4VL2ZTUF2KNHANCNFSM5FS52BCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
I use other containers as jackett, radarr or even plex and I don't have any problem with them. I'll check my docker config then |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, are you using any other network config with those containers?
…On Fri, Oct 8, 2021 at 16:49 Grégory Loyer ***@***.***> wrote:
I use other containers as jackett, radarr or even plex and I don't have
any problem with them. I'll check my docker config then
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1993 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7OFYRLCCWQ2JLMUEKJI7DUF2O7LANCNFSM5FS52BCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Nope. I use the bridge connection |
Beta Was this translation helpful? Give feedback.
-
|
As you see here: In your case, as you don’t use Dns override nothing has been changed, but dns lookup falls here, so something problematic with docker.. are you setting dns for those other containers? |
Beta Was this translation helpful? Give feedback.
-
|
any progress? |
Beta Was this translation helpful? Give feedback.
-
|
No nothing. i checked everything I don't understand why the DNS fails. So
now I just use regular transmission and I plug my syno on the VPN. Thx for
your help anyway
Le jeu. 14 oct. 2021 à 02:39, Patrick Kishino ***@***.***> a
écrit :
… any progress?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1993 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6SBPBCBCGRJEGQQ6NHLUDUGYRCJANCNFSM5FS52BCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
You might want to try and create a dedicated network instead of bridge network.. |
Beta Was this translation helpful? Give feedback.
-
|
I could do that indeed. I'm trying this as soon as I have time to start
over. Thanks a lot for your help
Cordialement,
Grégory LOYER
| mobile: 06.34.68.14.39
| email: ***@***.***
Le jeu. 14 oct. 2021 à 11:44, Patrick Kishino ***@***.***> a
écrit :
… You might want to try and create a dedicated network instead of bridge
network..
Are you perhaps using skynet or pihole etc where dns might bounce or so?
You could try and troubleshoot from inside the container by overriding
/etc/resolv.conf and adding nameserver 8.8.8.8 to it and see if dns will
resolve
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1993 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6SBPDNXYO4U7QZ2DMC5ITUG2RAHANCNFSM5FS52BCQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hello To get my DSM Docker to work I've had to do the following:
|
Beta Was this translation helpful? Give feedback.
-
|
I did read that latest dsm update should have fixed some issues with docker.. also, I don't recommend using the DSM docker app |
Beta Was this translation helpful? Give feedback.
-
|
Experiencing a similar problem. Did what you wrote, but it still fails with the following error: Starting container with revision: 76f7a2c |
Beta Was this translation helpful? Give feedback.
Hello
To get my DSM Docker to work I've had to do the following:
resolv.confat my /volume1/docker/custom_folder/ folder. Below is what I have written in the .conf