BakedPizza

I'm not sure what you mean. Are you wondering why I didn't have them set? If so, before the nextgen addition (and still true for the legacy endpoints on the latest version) they weren't mandatory anymore after the first start or if the credentials were mentioned in the ovpn file. Because I always manually linked them in the ovpn file and didn't like my username and password being logged on every start (supervisor.log), I removed these variables.

I was testing for hours today; almost tried all of the endpoints.... And then it hit me. What if I add the VPN_USER and VPN_PASS environment variables back (although the credentials.conf is there and set in the ovpn file). And *bam* no more "Unable to successfully download PIA json to generate token from URL". Apparently the environment variables are mandatory now. It does still work without them on the legacy endpoints. Is this how it's intended to work? I can imaging more people banging their heads because of this change... Glad it's working now, though.

Oh, I will, eventually. 😄 Something else; my legacy PIA config connects just fine but whenever I try to use the next-gen PIA config it's stuck at this step: Attached my log. I'm currently on 2.0.4.dev38_g23a48dd01-2-12. Am I doing something wrong, did I encounter a bug or is PIA messing with me? supervisord.log

Wireguard is new to me, so I'm just guessing based upon 1 hour of research; it looks like our linux kernel is too old. I'm at version 3.10 with DSM 6.2. Also, Synology doesn't provide official wireguard support while unraid does. I'm going to be honest here, Synology makes awesome all-in-one products with long-term support but I'm hitting the wall of possibilities. Time to move away and use my Synology unit as backup unit.

Any other issues besides the logs? I'm just guessing here. Take a look at your OpenVPN config file. Do you see a mention of verb? Is it verb 5 or higher? Change it to 4 or lower. From the OpenVPN documentation on verb 5: 5 — Output R and W characters to the console for each packet read and write, uppercase is used for TCP/UDP packets and lowercase is used for TUN/TAP packets.

I agree, but what can I say; we are talking about Synology. 🤷‍♂️ I was dumbfounded when they even added Docker support, as they always seem to like to keep things proprietary with little to no option to customize things. I will keep my mouth shut now, as I don't want to jinx it. It's working, that's what matters, right? *coughs*

@rinzes @Lipora @Ranzingabon Hagglesmith I've been away from this project for many months, but today I tried to get it up and running again, on my Synology NAS. And came across the same error you guys mentioned: /bin/bash: /root/init.sh: No such file or directory After running through all the code in the GitHub repositories, docker documentation, Google, etc, I almost gave up and did the most desperate thing you could do; search for the mention of /root/init.sh inside all my docker related files on my Synology NAS. And you know what? I messed up during the update. 😅 And I (hope and) think you guys did too. When using the export and import of the settings function in the Docker UI, it also exports the following line in the .json file: "cmd" : "/bin/bash /root/init.sh", Change this to the right line (below) and import the json file again, and you should be good to go! "cmd" : "/bin/bash /usr/local/bin/init.sh",

I'm using 1.3.15_14_gb8e5ebe82-1-11. I noticed multiple error logs on start after adding plugins to deluge: Can these be ignored or do I need to set the PYTHON_EGG_CACHE env? Debug level supervisord attached.

@ysu take a closer look at the two module warnings in the log. Sent from my D5503

@HanselI think so. Just turn it off if it's working fine. /home/nobody/getvpnip.sh # function to check ip adress is in valid format (used for local tunnel ip and external ip) [..] if [[ "${DEBUG}" == "true" ]]; then echo "[debug] Valid IP address from tunnel acquired '${current_vpn_ip}'" fi @ysu Please post your supervisord log (remove any credentials in the log). Not sure if I'm able to help, but others might. Ever found the time to do a request? Synology has a feature to link containers, so I'm very interested in a capability like this.

Could somebody explain the purpose of Privoxy (the version shipped in this container) to me? Any real-life use cases? My remote IP still seems to be visible when visiting https://www.dnsleaktest.com/ while using the proxy in Firefox.

@Hansel I think you are posting this in the wrong topic, as it seems you are using rtorrent and not deluge. I've got no experience with the rtorrent container. You should post your issues here: Or try switching to this container (arch-delugevpn).

Where do you see this? Inside the container or on your Synology NAS? I'm not seeing any AppArmor issues...

Sounds fair enough and thanks for your swift consideration. Time to look at your arch-medusa container.

To get this container to execute in Docker on the latest Synology version (DSM 6.1-15047 Update 1): The --cap-add=NET_ADMIN parameter isn't supported by the Docker GUI. Without it iptables won't play nice. Instead select 'Execute container using high privilege' under the General settings of the container. Make sure that mandatory kernel modules are loaded. We got two options (A & B): A. This won't survive a reboot. SSH as an user in the administrators group to your Synology NAS and run the following commands: sudo insmod /lib/modules/tun.ko sudo insmod /lib/modules/iptable_mangle.ko B. This will recover the loading during the boot. Create a new 'Triggered Task' from the DSM 'Control Panel' -> 'Task Scheduler'. Select user 'root', event 'Boot-up' and check 'Enabled'. As script enter: insmod /lib/modules/tun.ko insmod /lib/modules/iptable_mangle.ko Done. //EDIT: User reported he needed to reboot. I can't remember anymore. @binhex: Could you please consider adding an option to shutdown the container with a non-zero status if these modules are not loaded (if possible)? Currently the container appears to be running, but Deluge will not be loaded because of these missing modules. It took me some time to figure out why I couldn't reach Deluge. Also, Synology Docker contains and option (in the GUI) to auto restart the container on unexpected shutdown (non-zero exit status). I think it will append --restart failure to the docker command. If you add this shutdown we will always have enough time to make sure the loading of the required modules is done during the boot-up (using the Task Scheduler). Thank you so much for the container. The most used 3rd packages source for our Synology NAS systems (SynoCommunity) is currently incompatible with the latest version of the operation system (DSM 6+) and it looks like it will be the case for a long time. So containers like these are essential for us.