Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DSM 7 RC OVPN error opening config file #1839

Closed
6 tasks done
udrea93 opened this issue Jun 1, 2021 · 86 comments
Closed
6 tasks done

DSM 7 RC OVPN error opening config file #1839

udrea93 opened this issue Jun 1, 2021 · 86 comments
Labels
bug wontfix/not container problem Either a non-issue or related to 3PP

Comments

@udrea93
Copy link

udrea93 commented Jun 1, 2021 •
edited

Before creating this issue I have:

REQUIRED

  • Read through the pinned issues for related problems
  • Searched for similar provider issues and container issues
  • Read the documentation, especially the troubleshooting section and FAQ
  • Tried to add as much relevant information to the issue as possible
  • Verified I have tried using newest release as well
  • Agreed that my issue will be closed if I do not follow this template and will remain closed until I complete the template

Container version & last working release

Required, problem occurs in :

<DSM 7 RC>

If possible, last working version:

<DSM 7 Beta>

Describe the problem

REQUIRED

<-- Updated Synology to DSM 7 RC
Worked on Synology DSM 7 BETA
Can't connect to PrivateVPN ovpn -->

Describe the steps you have tried to solve the problem

REQUIRED

<-- 1) Update to latest version still persists
 2) Did a clean install  -->

Add your docker run command or docker-compose file or env details

REQUIRED

<-- OPENVPN_USERNAME= ******
OPENVPN_PASSWORD=******
OPENVPN_PROVIDER=PRIVATEVPN
OPENVPN_CONFIG=RO Bukarest
TRANSMISSION_WEB_UI=flood-for-transmission
TRANSMISSION_RPC_USERNAME=*****
TRANSMISSION_RPC_PASSWORD=*****
TRANSMISSION_RPC_AUTHENTICATION_REQUIRED=true -->

Logs

REQUIRED

<-- Starting container with revision: 3a193c4
Creating TUN device /dev/net/tun
Using OpenVPN provider: PRIVATEVPN
Starting OpenVPN using config RO Bukarest.ovpn
Setting OpenVPN credentials...
Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/privatevpn/RO Bukarest.ovpn
Use --help for more information. -->

Host system

REQUIRED

<-- Synlogy DSM 7 RC Docker 20.10.3-1231  -->
@udrea93 udrea93 added the bug label Jun 1, 2021
@github-actions
Copy link

github-actions bot commented Jun 1, 2021

@udrea93: hello! 👋

This issue is being automatically closed because it does not follow the issue template.
If you edit and follow the template properly by filling it in completely the issue will be re-opened

@github-actions github-actions bot closed this as completed Jun 1, 2021
@github-actions
Copy link

github-actions bot commented Jun 1, 2021

@udrea93: hello! 👋

This issue is being automatically closed because it does not follow the issue template.
If you edit and follow the template properly by filling it in completely the issue will be re-opened

@github-actions github-actions bot reopened this Jun 1, 2021
@TheBarron0
Copy link

also having the same issue with the above using Surfshark configurations

@egamer24
Copy link

egamer24 commented Jun 1, 2021

same issue with PIA, definitely an issue related to synology DSM 7 RC. beta was working normally

@matosconsulting
Copy link

matosconsulting commented Jun 1, 2021 •
edited

Piling on. I did attempt to work around this by manually mapping and seeing what happened, but no go.

To potentially help with tracking down the root of the issue, I did notice somewhat different behavior if I disable "execute container using high privilege" but start running in to some TUN/TAP problems. Unfortunately I do not have the time tonight to troubleshoot further or attempt to find a workaround, but if I figure anything out I'll share.

@pkishino pkishino added the wontfix/not container problem Either a non-issue or related to 3PP label Jun 2, 2021
@pkishino
Copy link
Collaborator

pkishino commented Jun 2, 2021

As above is showing, this does not seem to be a container issue but a problem with DSM. Please raise an issue with them.. I'll keep this open so you can report any updates etc

Out of interest, care to show the directory contents of /etc/openvpn/privatevpn/ including permissions etc (ls -haltr)

@TheBarron0
Copy link

managed to get this working today, disabled the option as above "execute container using high privilege", and then renabling it after failing and restarting seemed to redo the permissions and i have it running again.

Hope this helps someone else

@udrea93
Copy link
Author

udrea93 commented Jun 2, 2021

managed to get this working today, disabled the option as above "execute container using high privilege", and then renabling it after failing and restarting seemed to redo the permissions and i have it running again.

Hope this helps someone else

Works, thanks! But for some reson if i turn it off then back on i need to do it again as you explained.

@randomguy1991
Copy link

Same here. Occurred after updating to DSM 7 RC from beta. Checking off "execute container using high privilege", applying and trying to start the container, then turning it on afterwards work. However if you restart container, you have to do it again.

I did check if any files were present in /etc/openvpn/nordvpn/ but no file was ever created. Makes sense why it would fail at:
"Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/privatevpn/RO Bukarest.ovpn
Use --help for more information. -->"

Any ideas?

@jrodmonaco
Copy link

Doing this mentioned above allows my container to start but gives me the following error. Also after upgrading to RC:

NotADirectoryError: [Errno 20] Not a directory: '/docker/transmission/settings.json'

Any ideas? The directory is created.

@pkishino pkishino mentioned this issue Jun 4, 2021
Closed
@PrimeN
Copy link

PrimeN commented Jun 5, 2021

managed to get this working today, disabled the option as above "execute container using high privilege", and then renabling it after failing and restarting seemed to redo the permissions and i have it running again.

Hope this helps someone else

You deserve a medal. Thank you!

@DarrienG
Copy link

DarrienG commented Jun 5, 2021

Can confirm this worked for me as well. I had to disable: "Execute container using high privilege" and then let it crash once setting up whatever it was doing, and then re-enable right after.

@andreixk
Copy link

andreixk commented Jun 6, 2021

+1 issue started happening as soon as I upgraded to DSM7

@pkishino
Copy link
Collaborator

pkishino commented Jun 6, 2021

Will close for now as workaround found

@pkishino pkishino closed this as completed Jun 6, 2021
@pkishino pkishino pinned this issue Jun 6, 2021
@pkishino pkishino mentioned this issue Jun 7, 2021
Closed
6 tasks
@kknkkn1
Copy link

kknkkn1 commented Jun 7, 2021

@pkishino Hi Majestic Patrick
mine DS1819+ doesn't work even i tried above method...

date stream content
2021-06-07 12:31:24 stdout Use --help for more information.
2021-06-07 12:31:24 stdout Options error: Please correct these errors.
2021-06-07 12:31:24 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:31:24 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:31:24 stdout Setting OpenVPN credentials...
2021-06-07 12:31:24 stdout No VPN configuration provided. Using default.
2021-06-07 12:31:24 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:31:24 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:31:24 stdout Creating TUN device /dev/net/tun
2021-06-07 12:31:24 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:31:08 stdout Use --help for more information.
2021-06-07 12:31:08 stdout Options error: Please correct these errors.
2021-06-07 12:31:08 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:31:07 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:31:07 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:31:07 stdout Setting OpenVPN credentials...
2021-06-07 12:31:07 stdout No VPN configuration provided. Using default.
2021-06-07 12:31:07 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:31:07 stdout Creating TUN device /dev/net/tun
2021-06-07 12:31:07 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:30:14 stdout Use --help for more information.
2021-06-07 12:30:14 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:30:14 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:30:14 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:30:14 stdout Setting OpenVPN credentials...
2021-06-07 12:30:14 stdout No VPN configuration provided. Using default.
2021-06-07 12:30:14 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:30:14 stdout Creating TUN device /dev/net/tun
2021-06-07 12:30:14 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:29:50 stdout Use --help for more information.
2021-06-07 12:29:50 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:29:50 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:29:50 stdout Setting OpenVPN credentials...
2021-06-07 12:29:50 stdout No VPN configuration provided. Using default.
2021-06-07 12:29:50 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:29:50 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:29:50 stdout Creating TUN device /dev/net/tun
2021-06-07 12:29:50 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:52 stdout Use --help for more information.
2021-06-07 12:28:52 stdout Options error: Please correct these errors.
2021-06-07 12:28:52 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:28:52 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:51 stdout Setting OpenVPN credentials...
2021-06-07 12:28:51 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:51 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:51 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:28:51 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:51 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:29 stdout Use --help for more information.
2021-06-07 12:28:29 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:28:29 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:28:29 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:29 stdout Setting OpenVPN credentials...
2021-06-07 12:28:29 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:29 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:29 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:29 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:10 stdout Use --help for more information.
2021-06-07 12:28:10 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:28:10 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:09 stdout Setting OpenVPN credentials...
2021-06-07 12:28:09 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:09 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:09 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:28:09 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:09 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:24:28 stdout Use --help for more information.
2021-06-07 12:24:28 stdout Options error: Please correct these errors.
2021-06-07 12:24:28 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:24:28 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:24:28 stdout Setting OpenVPN credentials...
2021-06-07 12:24:28 stdout No VPN configuration provided. Using default.
2021-06-07 12:24:28 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:24:28 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:24:28 stdout Creating TUN device /dev/net/tun
2021-06-07 12:24:28 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:24:05 stdout Use --help for more information.
2021-06-07 12:24:05 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:24:05 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:24:05 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:24:05 stdout Setting OpenVPN credentials...
2021-06-07 12:24:05 stdout No VPN configuration provided. Using default.
2021-06-07 12:24:05 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:24:05 stdout Creating TUN device /dev/net/tun
2021-06-07 12:24:05 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:47 stdout Use --help for more information.
2021-06-07 12:23:47 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:23:47 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:47 stdout Setting OpenVPN credentials...
2021-06-07 12:23:47 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:47 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:46 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:23:46 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:46 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:19 stdout Use --help for more information.
2021-06-07 12:23:19 stdout Options error: Please correct these errors.
2021-06-07 12:23:19 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:23:19 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:19 stdout Setting OpenVPN credentials...
2021-06-07 12:23:19 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:19 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:19 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:23:19 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:19 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:04 stdout Use --help for more information.
2021-06-07 12:23:04 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:23:04 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:23:04 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:04 stdout Setting OpenVPN credentials...
2021-06-07 12:23:04 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:04 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:04 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:03 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:21:29 stdout Use --help for more information.
2021-06-07 12:21:29 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:21:29 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:21:29 stdout Setting OpenVPN credentials...
2021-06-07 12:21:29 stdout No VPN configuration provided. Using default.
2021-06-07 12:21:29 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:21:29 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:21:29 stdout Creating TUN device /dev/net/tun
2021-06-07 12:21:29 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:20:14 stdout Use --help for more information.
2021-06-07 12:20:14 stdout Options error: Please correct these errors.
2021-06-07 12:20:14 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:20:14 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:20:14 stdout Setting OpenVPN credentials...
2021-06-07 12:20:14 stdout No VPN configuration provided. Using default.
2021-06-07 12:20:14 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:20:14 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:20:14 stdout Creating TUN device /dev/net/tun
2021-06-07 12:20:13 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:19:56 stdout Use --help for more information.
2021-06-07 12:19:56 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:19:56 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:19:56 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:19:56 stdout Setting OpenVPN credentials...
2021-06-07 12:19:56 stdout No VPN configuration provided. Using default.
2021-06-07 12:19:56 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:19:56 stdout Creating TUN device /dev/net/tun
2021-06-07 12:19:56 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:19:40 stdout Use --help for more information.
2021-06-07 12:19:40 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:19:40 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:19:40 stdout Setting OpenVPN credentials...
2021-06-07 12:19:40 stdout No VPN configuration provided. Using default.
2021-06-07 12:19:40 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:19:40 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:19:40 stdout Creating TUN device /dev/net/tun
2021-06-07 12:19:40 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d

@kknkkn1
Copy link

kknkkn1 commented Jun 7, 2021

@pkishino Hi Majestic Patrick
mine DS1819+ doesn't work even i tried above method...

date stream content
2021-06-07 12:31:24 stdout Use --help for more information.
2021-06-07 12:31:24 stdout Options error: Please correct these errors.
2021-06-07 12:31:24 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:31:24 stdout 2021-06-07 12:31:24 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:31:24 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:31:24 stdout Setting OpenVPN credentials...
2021-06-07 12:31:24 stdout No VPN configuration provided. Using default.
2021-06-07 12:31:24 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:31:24 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:31:24 stdout Creating TUN device /dev/net/tun
2021-06-07 12:31:24 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:31:08 stdout Use --help for more information.
2021-06-07 12:31:08 stdout Options error: Please correct these errors.
2021-06-07 12:31:08 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:31:08 stdout 2021-06-07 12:31:08 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:31:07 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:31:07 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:31:07 stdout Setting OpenVPN credentials...
2021-06-07 12:31:07 stdout No VPN configuration provided. Using default.
2021-06-07 12:31:07 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:31:07 stdout Creating TUN device /dev/net/tun
2021-06-07 12:31:07 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:30:14 stdout Use --help for more information.
2021-06-07 12:30:14 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:30:14 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:30:14 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:30:14 stdout Setting OpenVPN credentials...
2021-06-07 12:30:14 stdout No VPN configuration provided. Using default.
2021-06-07 12:30:14 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:30:14 stdout Creating TUN device /dev/net/tun
2021-06-07 12:30:14 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:29:50 stdout Use --help for more information.
2021-06-07 12:29:50 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:29:50 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:29:50 stdout Setting OpenVPN credentials...
2021-06-07 12:29:50 stdout No VPN configuration provided. Using default.
2021-06-07 12:29:50 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:29:50 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:29:50 stdout Creating TUN device /dev/net/tun
2021-06-07 12:29:50 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:52 stdout Use --help for more information.
2021-06-07 12:28:52 stdout Options error: Please correct these errors.
2021-06-07 12:28:52 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:28:52 stdout 2021-06-07 12:28:52 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:28:52 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:51 stdout Setting OpenVPN credentials...
2021-06-07 12:28:51 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:51 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:51 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:28:51 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:51 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:29 stdout Use --help for more information.
2021-06-07 12:28:29 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:28:29 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:28:29 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:29 stdout Setting OpenVPN credentials...
2021-06-07 12:28:29 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:29 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:29 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:29 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:28:10 stdout Use --help for more information.
2021-06-07 12:28:10 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:28:10 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:28:09 stdout Setting OpenVPN credentials...
2021-06-07 12:28:09 stdout No VPN configuration provided. Using default.
2021-06-07 12:28:09 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:28:09 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:28:09 stdout Creating TUN device /dev/net/tun
2021-06-07 12:28:09 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:24:28 stdout Use --help for more information.
2021-06-07 12:24:28 stdout Options error: Please correct these errors.
2021-06-07 12:24:28 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:24:28 stdout 2021-06-07 12:24:28 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:24:28 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:24:28 stdout Setting OpenVPN credentials...
2021-06-07 12:24:28 stdout No VPN configuration provided. Using default.
2021-06-07 12:24:28 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:24:28 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:24:28 stdout Creating TUN device /dev/net/tun
2021-06-07 12:24:28 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:24:05 stdout Use --help for more information.
2021-06-07 12:24:05 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:24:05 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:24:05 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:24:05 stdout Setting OpenVPN credentials...
2021-06-07 12:24:05 stdout No VPN configuration provided. Using default.
2021-06-07 12:24:05 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:24:05 stdout Creating TUN device /dev/net/tun
2021-06-07 12:24:05 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:47 stdout Use --help for more information.
2021-06-07 12:23:47 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:23:47 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:47 stdout Setting OpenVPN credentials...
2021-06-07 12:23:47 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:47 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:46 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:23:46 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:46 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:19 stdout Use --help for more information.
2021-06-07 12:23:19 stdout Options error: Please correct these errors.
2021-06-07 12:23:19 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:23:19 stdout 2021-06-07 12:23:19 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:23:19 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:19 stdout Setting OpenVPN credentials...
2021-06-07 12:23:19 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:19 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:19 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:23:19 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:19 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:23:04 stdout Use --help for more information.
2021-06-07 12:23:04 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:23:04 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:23:04 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:23:04 stdout Setting OpenVPN credentials...
2021-06-07 12:23:04 stdout No VPN configuration provided. Using default.
2021-06-07 12:23:04 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:23:04 stdout Creating TUN device /dev/net/tun
2021-06-07 12:23:03 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:21:29 stdout Use --help for more information.
2021-06-07 12:21:29 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:21:29 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:21:29 stdout Setting OpenVPN credentials...
2021-06-07 12:21:29 stdout No VPN configuration provided. Using default.
2021-06-07 12:21:29 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:21:29 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:21:29 stdout Creating TUN device /dev/net/tun
2021-06-07 12:21:29 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:20:14 stdout Use --help for more information.
2021-06-07 12:20:14 stdout Options error: Please correct these errors.
2021-06-07 12:20:14 stdout Options error: --auth-user-pass fails with '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 WARNING: cannot stat file '/etc/openvpn/custom/auth.txt': No such file or directory (errno=2)
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
2021-06-07 12:20:14 stdout 2021-06-07 12:20:14 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-06-07 12:20:14 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:20:14 stdout Setting OpenVPN credentials...
2021-06-07 12:20:14 stdout No VPN configuration provided. Using default.
2021-06-07 12:20:14 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:20:14 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:20:14 stdout Creating TUN device /dev/net/tun
2021-06-07 12:20:13 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:19:56 stdout Use --help for more information.
2021-06-07 12:19:56 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:19:56 stdout RTNETLINK answers: Operation not permitted
2021-06-07 12:19:56 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:19:56 stdout Setting OpenVPN credentials...
2021-06-07 12:19:56 stdout No VPN configuration provided. Using default.
2021-06-07 12:19:56 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:19:56 stdout Creating TUN device /dev/net/tun
2021-06-07 12:19:56 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d
2021-06-07 12:19:40 stdout Use --help for more information.
2021-06-07 12:19:40 stdout Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/custom/default.ovpn
2021-06-07 12:19:40 stdout adding route to local network 192.168.2.0/24 via 172.17.0.1 dev eth0
2021-06-07 12:19:40 stdout Setting OpenVPN credentials...
2021-06-07 12:19:40 stdout No VPN configuration provided. Using default.
2021-06-07 12:19:40 stdout Using OpenVPN provider: CUSTOM
2021-06-07 12:19:40 stdout mknod: /dev/net/tun: File exists
2021-06-07 12:19:40 stdout Creating TUN device /dev/net/tun
2021-06-07 12:19:40 stdout Starting container with revision: 69b4d182671a60012cfee8b8cc557ebd2d664d5d

now i fixed,,
by multiple trying to change privilege authority and symbolic link for /etc/openvpn/custom/default.ovpn

@mdstoll
Copy link

mdstoll commented Jun 7, 2021

Seems to work! However with the large amount of files I have in transmission, it crashes every now and then. This isn't an issue, however, at this point after crashing it starts to loop and manual labour is required to get it working again.

Now, I understand as mentioned this is probably some synology specific issue, that should be fixed by another party. However, other containers work. In case a solution is (or will be) found, I'd like to know :)

@andreixk
Copy link

The workaround is failing also - transmission stopped downloading, when i tried to restart the container, it started crashing because of the same error. This bug is present, the workaround is at best a temporary patch that holds for a day or so.

@pkishino
Copy link
Collaborator

pkishino commented Jun 11, 2021 via email

@TheBarron0
Copy link

Repeating the steps of the workaround will get the container running again. Done it multiple times. Will have to do until Synology fix the issues with RC

@Silversurfer79 Silversurfer79 mentioned this issue Sep 7, 2021
Closed
6 tasks
@Silversurfer79
Copy link

Please see this for PriavteVPN hard and soft failure authtication issues using Transmission, Docker and Portainer
haugene/vpn-configs-contrib#42

@StormPooper StormPooper mentioned this issue Sep 10, 2021
Open
@good3n
Copy link

good3n commented Sep 20, 2021

Will close for now as workaround found

Is there a more permanent solution to this? This has to be done every time the container stops.

@randomguy1991
Copy link

Will close for now as workaround found

Is there a more permanent solution to this? This has to be done every time the container stops.

Well I used the Portainer method to re-creating my docker image and since then, I didn’t have anymore issues. I have watch-tower that updates my container without issues and restarted my NAS a couple times for updates without any issues with the containers starting up.

This is a Synology docker issue. I think the best solution is creating the docker either through Portainer or command.

@pkishino pkishino mentioned this issue Oct 10, 2021
Closed
8 tasks
@adamtee
Copy link

adamtee commented Oct 31, 2021

These instructions were helpful https://github.com/haugene/docker-transmission-openvpn/issues/1839#issuecomment-894724920 but to expand on it for total noobs like myself and make it easy here is what I did after 2 days of ripping my hair out.

  1. Installed haugene/transmission-openvpn using Docker in DSM
  2. Installed Portainer using this guide https://www.portainer.io/blog/how-to-install-portainer-on-a-synology-nas
  3. Logged into Portainer, located the image and clicked Duplicate/Edit
  4. Select Capabilities and toggle ON the setting NET_ADMIN
  5. Select Runtime & Resources and toggle OFF the setting Privileged mode
  6. Deploy the container and let it replace the existing one.

I hope this helps

@Doryx3D
Copy link

Doryx3D commented Nov 2, 2021

  1. Installed Portainer using this guide https://www.portainer.io/blog/how-to-install-portainer-on-a-synology-nas
  2. Logged into Portainer, located the image and clicked Duplicate/Edit
  3. Select Capabilities and toggle ON the setting NET_ADMIN
  4. Select Runtime & Resources and toggle OFF the setting Privileged mode
  5. Deploy the container and let it replace the existing one.

This is no more necessary since latest Synology Docker update (version 20.10.3-1239). Now you can enable NET_ADMIN from Edit > config functionality > check NET_ADMIN
image

Since the update, the container has worked flawless.

@bensquire
Copy link

bensquire commented Nov 3, 2021 •
edited

This is no more necessary since latest Synology Docker update (version 20.10.3-1239). Now you can enable NET_ADMIN from Edit > config functionality > check NET_ADMIN

@doryxbirb Cracking advice, thanks.

@ultimateguy
Copy link

This is no more necessary since latest Synology Docker update (version 20.10.3-1239). Now you can enable NET_ADMIN from Edit > config functionality > check NET_ADMIN

This doesn't work for me... I have this version of Docker, checked off NET_ADMIN, and the container crashes on startup like it did before.

@Doryx3D
Copy link

Doryx3D commented Nov 23, 2021

This doesn't work for me... I have this version of Docker, checked off NET_ADMIN, and the container crashes on startup like it did before.

I have just tried:
2021-11-23 11:33:28,stdout,STARTING TRANSMISSION
2021-11-23 11:33:28,stdout,Transmission startup script complete.
2021-11-23 11:33:28,stdout,Tue Nov 23 12:33:28 2021 Initialization Sequence Completed

It works if your problem was about TUN device creation or something fixable using full admin permissions.
Check your log to see what the actual problem is.

@rushapoil
Copy link

i believe you got it wrong, he didn't say you can now check off, he said now you can check it from synology docker app, instead of toying around with portainer or else, which is new

@ultimateguy
Copy link

Sorry, I think I get it now. This is the error I'm getting in the log.
Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/pia/ca_toronto.ovpn

If I understand correctly, Portainer is the permanent fix?

@DarrienG
Copy link

For me after adding NET_ADMIN it failed on the first run, but worked perfectly every run after that. If it isn't in a crashloop, consider just letting it do its thing and the container will probably start fine on the second attempt.

@Silversurfer79
Copy link

Well since moving away from Docker to do my management and moved to Portainer I havnt had a single issue, I have the latest build of Trasmission on a Synology NAS updating it using Watchtower. Its been like butter with PriavteVPN. I would strongly urge you to do the same. Find a Portainer install on sysnolgy nas video on Youtube. - https://www.youtube.com/watch?v=ToL5SPFUPaQ&t=805s.

Opens IPA and puts feet up.

My config using Stacks:


version: '3.3'


services:
  transmission:
    image: haugene/transmission-openvpn:latest
    restart: unless-stopped
    cap_add:
     - NET_ADMIN


    ports:
      - 9091:9091 # http://nas-ip:9091 to access ui
      - 8888:8888 # web-proxy


    environment:
    - LOCAL_NETWORK=192.168.0.0/24
    - OPENVPN_CONFIG=stockholm-sweden-allportfwd
    - OPENVPN_USERNAME=YOURCREDSHERE
    - OPENVPN_PASSWORD=YOUPASSWORDHERE
    - OPENVPN_PROVIDER=PRIVATEVPN # PIA or etc
    - CREATE_TUN_DEVICE=true
    - HEALTH_CHECK_HOST=PRIVATEVPN.com
    - OPENVPN_OPTS=--inactive 3600 --ping 20 --ping-exit 120
    - TRANSMISSION_WEB_UI=transmission-web-control
    - PUID=100 (check what yours is)
    - PGID=1000 (check what yours is)
    - TRANSMISSION_BLOCKLIST_ENABLED=true
    - TRANSMISSION_BLOCKLIST_URL="http://list.iblocklist.com/?list=ydxerpxkpcfqjaybcssw&fileformat=p2p&archiveformat=gz"
    - TRANSMISSION_DOWNLOAD_QUEUE_ENABLED=true
    - TRANSMISSION_DOWNLOAD_QUEUE_SIZE=5
    - TRANSMISSION_ENCRYPTION=2
    - TRANSMISSION_PEX_ENABLED=false
    - TRANSMISSION_DHT_ENABLED=false
    - TRANSMISSION_LPD_ENABLED=false
    - TRANSMISSION_ALT_SPEED_DOWN=10240
    - TRANSMISSION_ALT_SPEED_ENABLED=true
    - TRANSMISSION_ALT_SPEED_TIME_BEGIN=420
    - TRANSMISSION_ALT_SPEED_TIME_DAY=127
    - TRANSMISSION_ALT_SPEED_TIME_ENABLED=true
    - TRANSMISSION_ALT_SPEED_TIME_END=1439
    - TRANSMISSION_ALT_SPEED_UP=1024
    - TRANSMISSION_MAX_PEERS_GLOBAL=250
    - TRANSMISSION_PEER_ID_TTL_HOURS=6
    - TRANSMISSION_PEER_LIMIT_GLOBAL=250
    - TRANSMISSION_PEER_LIMIT_PER_TORRENT=50

    - TRANSMISSION_RATIO_LIMIT=1
    - TRANSMISSION_RATIO_LIMIT_ENABLED=true

    volumes:
    - /volume1/docker/transmission-openvpn/resolv.conf:/etc/resolv.conf:ro # use to stop dns-leak
    - /volume1/Media/Downloads/Complete:/completed # change to download dir
    - /volume1/docker/transmission-openvpn:/data
    - /volume1/docker/transmission-openvpn:/config
    - /volume1/Media/Downloads/Watch:/watch
    - /volume1/Media/Downloads/Incomplete:/incomplete
    - /etc/localtime:/etc/localtime

@ultimateguy
Copy link

Thanks! I seem to have it working with Portainer now. I'll have to check out Watchtower as well.

@Silversurfer79
Copy link

Silversurfer79 commented Nov 23, 2021 •
edited

To be clear, Portainer is a container that runs on Docker (this isnt made clear or obvious when you set out anywhere), it allows for a lot more flexibility and more advanced config of containers with features like Stacks. I mean in Docker you would have to pull down a new image of the container you would like to update, assuming you knew there was a update. Then copy the containers, renaming the exciting one to old and then starting the new one which intern uses the new image, then do image clean-up after. In Portainer you select the container, click Recreate and select pull latest image and you done 10 seconds later. Its even easier use Watchtower, it checks for you when new containers arrive, it can send you messages, via Mail, Teams etc. and at the intervals of your choice and automatically update your containers when they get updates... that’s it...

This isn’t just a pain, that I can tell you, but a game changer!

@kirksw
Copy link

kirksw commented Nov 23, 2021

Glad to see that Synology added more options to the UI. But to anyone in this discussion, I highly recommend you don't use their crippled UI, truly learning the docker tooling will reward you much more in the long-term. Then you aren't restricted to deploying on Synology devices - you can deploy to any Linux device, or the even the cloud.

@HavermansStef
Copy link

@kirksw Just use the method you prefer. Not everyone wants to know the technical side of an action, some just want speed and an interface. For what it's worth, I personally think the Docker Synology interface is a great addition for people who don't want to mess around in the command line.

@pkishino
Copy link
Collaborator

pkishino commented Dec 2, 2021 via email

@ultimateguy
Copy link

Anyone willing to share their docker command for this container? I'm interested in ditching the Synology GUI in favor of CLI.

@Silversurfer79
Copy link

Anyone willing to share their docker command for this container? I'm interested in ditching the Synology GUI in favor of CLI.
See above in the thread, #1839 (comment)

@Silversurfer79
Copy link

Glad to see that Synology added more options to the UI. But to anyone in this discussion, I highly recommend you don't use their crippled UI, truly learning the docker tooling will reward you much more in the long-term. Then you aren't restricted to deploying on Synology devices - you can deploy to any Linux device, or the even the cloud.

Because I started using Docker and now Portainer, I have dived into the world of containers and finding so many useful products and services. I think the two thumbs down is no necessary consider this sis all free and people give their time here at no cost.

@Silversurfer79
Copy link

There is no getting away from it, put your big pants on and get on with it.

@jtarvainen
Copy link

jtarvainen commented Dec 29, 2021 •
edited

I wonder if I'm the only one who hasn't been able to resolve this issue? I'm running DSM 7 on an ARM-based Synology NAS. I'm actually using a slightly different image (guillaumedsde/alpine-qbittorrent-openvpn), but I wanted to comment here since the issue is exactly the same and this is the most extensive discussion I've found on the topic.

I've tried every solution mentioned in this thread, but I still get either of the following errors:

privileged: true ->

Options error: In [CMD-LINE]:1: Error opening configuration file: /config/openvpn/config.ovpn

privileged: false ->

ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)

Here's my full docker-compose.yml file:

version: "3.3"
services:
  alpine-qbittorrent-openvpn:
    image: guillaumedsde/alpine-qbittorrent-openvpn:latest
    container_name: qbittorrent
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    environment:
      - PUID=1000
      - PGID=1000
      - LAN=192.168.0.0/16
      - OPENVPN_PROVIDER=EXPRESSVPN
      - OPENVPN_CONFIG=<config>
      - OPENVPN_USERNAME=<username>
      - OPENVPN_PASSWORD=<password>
    network_mode: host
    ports:
      - "8080:8080"
    privileged: true
    volumes:
      - "/volume1/docker/alpine-qbittorrent-openvpn/config:/config"
      - "/volume1/media/downloads:/downloads"
      - "/etc/localtime:/etc/localtime:ro"

One thing I haven't seen mentioned in this thread is the use of network_mode: host. I've been under the impression that at least for ARM-based Synology devices, the only way to run Docker is in "host" network mode. In any case, I've been unable to get any other mode to work. Have I missed something?

Thanks in advance for any help!

@pkishino pkishino mentioned this issue Jan 1, 2022
Closed
8 tasks
@domigi
Copy link

domigi commented Jan 2, 2022

I tried all possible solutions mentioned above, sadly none did the trick.
I now changed my version tag from latest (4.0) to 3.71 and it's working again, without "execute container using high privilege".

So I'm not 100% certain this issue has to do with DSM7 as I am also running it and don't have issues with lower releases.

@dglwilkins
Copy link

I tried all possible solutions mentioned above, sadly none did the trick. I now changed my version tag from latest (4.0) to 3.71 and it's working again, without "execute container using high privilege".

So I'm not 100% certain this issue has to do with DSM7 as I am also running it and don't have issues with lower releases.

This fixed it for me as well

@pkishino pkishino unpinned this issue Aug 29, 2022
@wattsra
Copy link

wattsra commented Oct 4, 2022

Downgrading from version 4 was the only solution that worked fore as well.
The latest version would boot loop complaining that the .ovpn files didn't exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug wontfix/not container problem Either a non-issue or related to 3PP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests