HelpRequester
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by HelpRequester
-
-
26 minutes ago, wgstarks said:
There is nothing to configure for this. You just need to connect to an endpoint from your VPN provider which supports port forwarding.
According to the documentation of my VPN provider, all their servers offer port forwarding so this should not be an issue.
This site describes how to use it: https://vnm.windscribe.net/support/article/37/what-is-ephemeral-port-forwarding-and-how-to-use-it
As I have mentioned, it seems the thing I'm missing is the correct internal port that deluge is using.
-
9 hours ago, Lipora said:
#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?
1. The way it works with my VPN provider is that I have to select which port to forward. I enter the what they call the "internal port" to forward and that gets mapped to an external port, either the same number port that I select or a random based on my choosing. My problem is that I don't know what my internal port is supposed to be in this scenario. I tried setting one in Preferences -> Network -> Incoming Port and then forwarding that port at my VPN provider but it did not lead to any speed increase. From the opening posts by binhex in this thread, it seems that port forwarding is essential to reach your maximum speed potential, unfortunately I don't yet know the right ones to choose.
2. This I was able to fix. I entered the path "/data" as my desired download location and now new downloads show up there. I was able to move my completed torrents by selecting the "move download folder" option from within Deluge. I still don't know where from it moved the downloads but they did get moved into the desired folder so I guess it ultimately matters little.
-
Having done some more testing, I have run into two new issues.
1. My speeds are quite slow, around 2.5 MiBs per second at most, I understand that I might need to forward a port at my VPN provider to improve speeds, however, I don't know where to find which port I need to forward. I have tried going into Preferences -> Network -> Incoming Port and specifying a port there (the default was 0) and then forwarded the port at my VPN provider, this did not lead to a speed increase tho.
2. I don't know where my completed downloads are. In the deluge settings there is the default download path of "/home/nobody/Downloads" but in the File Manager of my NAS, I can't find such a path. The file structure of my NAS looks like this:
DS918plus
-docker
-downloads
--complete
---torrents
-otherAnd I have configured the following mounts in the docker container:
Folder - Mount
downloads/complete/torrents - /data
docker/deluge - /configI would like to move the already completed downloads in the downloads/complete/torrents folder but can't find them. I would also like to set the same folder as the default for future downloads but don't know what I need to enter in deluge in order to achieve that.
Any advice would be much appreciated.
-
42 minutes ago, Lipora said:
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.
Happy to report that the routing through the VPN works correctly, as the IP check does not show my real IP address. My VPN provider unfortunately doesn't offer DNS servers, meaning I'll have to make do with public ones. I already have a lifetime license so switching providers would not be a financially prudent move, I just hope the VPN itself will offer enough of added privacy/security.
-
19 minutes ago, Lipora said:
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.
Changing the DNS server allowed me to finally connect to the deluge webui and now I am able to download. Your help has been essential in getting this up and running, thank you very much.
Is there an easy check I can make to be sure the torrent traffic is going through the VPN correctly and I've also not accidentally made my network more vulnerable to intrusions?
-
3 minutes ago, Lipora said:
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
Thank you for swift reply. I have set the entry NAME_SERVERS as 192.168.1.1 since that's what my DNS Server is according to "ipconfig /all".
-
9 hours ago, Lipora said:
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.
Thank you very much for the tip Lipora, I did as you suggested and the error message about the TUN/TAP not being found has disappeared from my logfile! However, I have encountered a new error which reads as follows:
2019-08-30 14:34:44,545 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment2019-08-30 14:34:44,545 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...2019-08-30 14:34:44,554 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...From this I understand there to be a connection issue, could this be tied to the DNS Server I have configured? My DNS servers are set up in my router to be automatically assigned by my ISP. I have gone into CMD and entered "ipconfig /all", there it told me the DNS server was 192.168.1.1 which is what I have entered into the configuration of the delugevpn docker container. Is this incorrect? I don't need to access deluge or indeed any of my NAS from outside my home network, I only want to be able for the NAS to download and seed torrents after I add them at home.
-
I am humbly seeking assistance in setting up the DelugeVPN docker container on a Synology DS918+ NAS system. I have followed the guide from here as best I could:
http://tomthegreat.com/2018/03/11/setting-up-deluge-with-vpn-on-synology-using-docker/
Unfortunately, I am unable to access the Deluge setup wizard after going through the process (Step 12). Looking at the supervisord.log file, it seems the problem is related to this:
DEBG 'start-script' stdout output:
ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)
Exiting due to fatal errorI have attached the logfile in it's entirety in the hopes of finding help in this matter. My computer skills are limited and thus I don't see a of way fixing this on my own.
Thank you for your consideration.
[Support] binhex - DelugeVPN
in Docker Containers
Posted
I used this site:
https://www.portcheckers.com/
with the IP that my tracker reports that I'm using (the one that, from my understanding, is the VPN one as it differs from the one that's reported for my desktop) and the port I have forwarded at my VPN provider as well as set as the incoming port in the Deluge settings. When doing this, the site reports the port as open, does this mean that my slow down- and upload speeds are caused by something other than port forwarding?