#Torguard deluge client how to#
#Torguard deluge client update#
#Torguard deluge client code#
#Torguard deluge client Pc#
#Torguard deluge client download#

My connection is 20Mb/s DL and approx 1Mb/s UL, and i see typically 850 KB/s to 1.3 MB/s DL speeds, it doesnt overly bother me, and for the cost of PIA (which is very low if you pay yearly) im happy enough for now. I'm just curious if there is anything I can change to improve my speeds? port forwarding perhaps?Īs far as i know there are no further tweaks you can make to the ovpn config file to improve speeds, your options really are try different gateways or switch provider, do keep in mind though there will always be an overhead when using a vpn tunnel whatever provider you go with, so you might just have to accept this is the cost of anonymity and leave it at that. I have tried a number of known fast torrents, ie several linux distros, in an attempt to max out my connection, as i understand torrents being torrents arent always reliable for speed, and still topped out at around the 3MB mark. this would indicate that I am losing or not making use of a further 6-8MB.

#Torguard deluge client Pc#

I connect to the PIA VPN with my W10 pc and ran a speed test which showed 100mb and 20mb up to my chosen server.

#Torguard deluge client download#

I can not seem to get any faster than 3MB download speeds. I am having some issues with download speeds. Hi and welcome to unRAID forums!, your going to love it here, people are friendly and knowledgeable, best forum ive ever been on for sure!.įirstly thanks for the great apps. Let me know if there's anything else you guys need as far as info and thanks again. LAN_RANGE mynetworklan.3-mynetworklan.3.254 Wed Jan 27 23:16:55 2016 WARNING: file 'nf' is group or others accessible

#Torguard deluge client update#

Wed Jan 27 23:16:55 2016 DEPRECATED OPTION: -tls-remote, please update your configuration A OUTPUT -p icmp -m icmp -icmp-type 8 -j ACCEPT A OUTPUT -p udp -m udp -dport 53 -j ACCEPT A OUTPUT -o eth0 -p tcp -m tcp -sport 8112 -j ACCEPT A OUTPUT -o eth0 -p tcp -m tcp -dport 8112 -j ACCEPT A OUTPUT -o eth0 -p udp -m udp -dport 443 -j ACCEPT A INPUT -p icmp -m icmp -icmp-type 0 -j ACCEPT A INPUT -p udp -m udp -sport 53 -j ACCEPT A INPUT -i eth0 -m iprange -dst-range myserverports- myserverports.254 -j ACCEPT A INPUT -i eth0 -m iprange -src-range myserverports- myserverports.254 -j ACCEPT A INPUT -i eth0 -p tcp -m tcp -sport 8112 -j ACCEPT A INPUT -i eth0 -p tcp -m tcp -dport 8112 -j ACCEPT

A INPUT -i eth0 -p udp -m udp -sport 443 -j ACCEPT I have the ca. file as well as the ovpn file sitting in mnt/cache/ Any help would be greatly appreciated as the rest of this process has been incredibly awesome. I'm using IPVanish as my vpn and have gone into the advanced settings to get everything properly set up based on these threads. I feel like I've gotten most of my docker apps setup and running without a hitch, the one I can't seem to figure out is DelugeVPN from binhex. I've recently made the move from FreeNAS to Unraid and I'm trying to get used to the whole docker setup. Hi Binhex! I posted in /plugins (v6), but was told to post here as well. If you wish to rollback to Deluge 1.x then follow Q5. Private trackers may not of vetted deluge 2.x as a torrent client and thus it may not be permitted to connect to the track at this time (check with your private site admin).

#Torguard deluge client how to#

There is currently no Deluge thin client v2.x for Mac or Windows, and Deluge 1.x thin clients cannot communicate with Deluge v2.x server, if you are using the thin client from either of these platforms then currently you will have to rollback to Deluge v1.x to be able to connect (see below for how to do this). The current workaround is to use blackhole/watch folder and get Deluge v2.x to pickup torrents from there.Īs Deluge v2.x is re-written for Python 3.x the current Deluge v1.x plugins will NOT work with Deluge v2.x until they have been re-coded, thus if you rely on specific 3rd party Deluge plugins then you may want to roll back to Deluge v1.x (see below for how to do this).

#Torguard deluge client code#

IMPORTANT - Deluge 2.x compatibility issuesĭeluge v2.x has now been released, as this is a MAJOR code re-write certain things will currently not work until they are re-coded:-Ĭouchpotato at this time looks to be unable to communicate with deluge 2.x (even against latest commits to master), no information shown in log, even if logging level set to debug.