Can’t start on Synology

[Gitcrt5]

I have just tried installing this on a Synology DS918+. I am no expert so just tried to do the basics. My Docker is new. It is the only package. I downloaded this package and set it up to use PIA. When I start it I get an error in the log :
Options error: the --route-pre-down directive should have at most 1 parameter
Then it stops. I have followed the steps listed for trouble shooting at https://haugene.github.io/docker-transmission-openvpn/debug/ and they all work. I'm not sure what I need to do or edit.

[pkishino]

Post the whole log please

[2b-arc]

I have the same issue.
haugene-transmission-openvpn-2.csv

[pkishino]

your using nordvpn and don't look like you setup config properly, check the documentation please...

[wildoracle]

I'm having the same problem as well, and this is so frustrating because I had similar issues when first setting this up years ago. It had been running just fine, until Synology Container Manager told me I needed to update the container. After doing that, it won't start again. I should have followed the old adage, "if it ain't broke don't fix it".
Now the container starts and then stops. I had to go through hoops and hurdles back when I set it up, following this guide to create a TUN.sh startup script, and selecting the "execute container using high privilege" in order to get things working
I've tried everything I can find. Attached is my log file.
haugene-transmission-openvpn.csv
THANK YOU!

[Gitcrt5]

Here is the log.
haugene-transmission-openvpn1.csv

[pkishino]

Please also post your config, seems like the error is in the config

[Gitcrt5]

I didn't use a configuration file, I set it up in the docker package on technology by putting in the details in the docker GUI environment section. I found these files in the docker subdirectory, is this what you mean?

[pkishino]

you just uploaded your vpn credentials..I deleted the post but you best change them anyway

[Gitcrt5]

[pkishino]

yes, your config is bad..
OPENVPN_OPTS you have modified, you should specify the config in OPENVPN_CONFIG

[pkishino]

like this
-e OPENVPN_PROVIDER=PIA
-e OPENVPN_CONFIG=france
-e OPENVPN_USERNAME=user
-e OPENVPN_PASSWORD=pass \

[pkishino]

https://haugene.github.io/docker-transmission-openvpn/config-options/

[Gitcrt5]

If you have a look at my screenshot there is no OPENVPN_CONFIG field to use. I only filled in the options that were available to me.

[Gitcrt5]

Ahh. I see. You can edit those options. Sorry, I did not know that. It was presented as an option to fill out and I did not think to edit it. I'll try that now.

[pkishino]

Please look at the documentation, The dsm gui is a terrible tool for this and you most likely need to create the field yourself or rename the openvpn_opts field

…

On Fri, 8 Dec 2023 at 13:35, Gitcrt5 ***@***.***> wrote: If you have a look at my screenshot there is no OPENVPN_CONFIG field to use. I only filled in the options that were available to me. — Reply to this email directly, view it on GitHub <#2752 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OFYWX46L526DYQV4NYMDYIKKI3AVCNFSM6AAAAABAKSNMX6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOOJWGA4DA> . You are receiving this because you commented.Message ID: <haugene/docker-transmission-openvpn/repo-discussions/2752/comments/7796080 @github.com>

[Gitcrt5]

Thanks. Not being an advanced user I just went with the easiest way forward for me. I thought of using a config file but it wasn't clear to me where I should put it. And if I did want to use a config file how I would tell Docker to use that file rather than the options from the GUI.

[pkishino]

please look at dsm forums or support for dsm as that docker package is built for dsm, I do not know

…

On Fri, Dec 8, 2023 at 1:48 PM Gitcrt5 ***@***.***> wrote: Thanks. Not being an advanced user I just went with the easiest way forward for me. I thought of using a config file but it wasn't clear to me where I should put it. And if I did want to use a config file how I would tell Docker to use that file rather than the options from the GUI. — Reply to this email directly, view it on GitHub <#2752 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7OFYS45NCZIU2P4L2S5KDYIKLZTAVCNFSM6AAAAABAKSNMX6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOOJWGE2DS> . You are receiving this because you commented.Message ID: <haugene/docker-transmission-openvpn/repo-discussions/2752/comments/7796149 @github.com>

[Gitcrt5]

Tried again. Still failed. Logs etc included.
haugene-transmission-openvpn1 (1).json
haugene-transmission-openvpn1.csv

[pkishino]

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

please check on dsm forums or such, this is a permission problem..

[Gitcrt5]

OK. Thanks for all of your help.

[metaclam]

I'm in a very similar boat Gitcrt5. I agree that using the Container Manager GUI would be far simpler to use, but why does it populate with irrelevant or incorrect "deafult" keys? That's coming from where?

Anyway did you get any answers on any dsm forums?

[borland502]

If anyone finds this thread and had to follow the faq to avoid a soft reset and is using a docker-compose:

- OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60 --pull-filter ignore ping

should not have any quotes, contrary to the container log's advice