Lipora

No nothing yet. Was hoping to see an update possibly from BinHex but notta...

#1 - So VPN's like this usually have special options for Port Forwarding. It will depend on your VPN provider and what they have set...this Deluge Client I haven't seen the ability to facilitate the Port Forwarding. It may not be possible but I'll defer to anyone else on this one. I can't see how it could work based on how Docker Containers work with Networking. #2 - You have to consider that the container has its own "Special File System" that only exists inside the container. When you setup your folder mounts this is a way to "map" one of the folders you have outside of the container, into the container. From the mounts I see, It looks like you are mounting your "Downloads/complete/torrents" folder into a folder inside the container called /data. What that means is that in Deluge you want your completed downloads to be placed into the /data folder and then you will see that in your Synology in the Downloads/Complete/Torrents folder. From there you can point plex at that folder or do your post processing on that folder and move them into a media library. Are you using other containers that need to interact with these files? i.e. Sonarr and Radarr? or just the downloader?

So two things you should do: 1. Use a "Check my IP" Torrent Site like http://checkmyip.torrentprivacy.com/ You need to do the "BitTorrent Proxy Option" on that site. It has you start a torrent download and then shows the IP address that the Torrent shows you working from. As long as the IP it shows you is not the same as google reports your IP to be then you are good. 2. Second thing to do is to make sure you are using the right DNS server for your VPN provider. Just using 8.8,8,8 is a great test to get things working but to truly hide your DNS lookups you'll need to use one from your VPN provider. The first step will check that your torrents are truly going through the VPN. The second one just plugs you from DNS leaks that can still trace back your traffic to you. With BixHex's client you are essentially making a direct VPN between your Downloader and your VPN provider so you shouldn't need to worry about becoming "more vulnerable" there is still the possibility of someone gaining access to your docker container but it is a much smaller attach surface and the container itself can be easily "reset" by stopping and starting the container.

192.168.1.1 is what your router hands out internally. try changing 192.168.1.1 to 8.8.8.8 which is a Google DNS server.. If that works then I would find out the DNS servers you are to use for your VPN provider and switch it to those. i.e. for PIA they want you to use: 209.222.18.222 and 209.222.18.218.

That is most likely the DNS servers you set in your Docker Config. The container uses those. Do you have them set as: Name_Servers = 209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4

Hey Help Requestor... You need to get the Tunnel Adapter up and running on the synology. The guide has a "tun.sh" file that it has you create. That tend's not to work on newer versions of DSM. The work around I found is to setup a Scheduled Task to basically run "sudo insmod /lib/modules/tun.ko" instead of launching the tun.sh. I have mine setup to run on a schedule at midnight. Only thing you need to be aware of, is if you reboot your NAS you might need to run the task manually to kick off the tunnel adapter before docker launches Deluge+VPN.... I couldn't get it to run properly on Boot up as the instructions show.

Hello BixHex, I just updated to the latest version a few days ago and I cannot get it running on my Synology. I've been using the previous versions for some time but this one has started giving me grief. When I start the docker container I get the error: /bin/bash: /root/init.sh: No such file or directory It's as though it's trying to run the inital run script to see that all the previous config files are in place etc. but not being able to do so as it cannot locate that /root/init.sh location on the synology. I know Synology Docker is a bit different than others with its file locations but most containers I've been able to get working. This one I'm struggling with. Any advise would be helpful. Added: Found a reference to the fact that /bin/bash might not be available in Synology Docker?! It’s because bash is not part of the image. Launching shell with /bin/sh would work. However, I don’t know if it’s possible to configure that on Synology... Any help would be great.