craigr

lotetreemedia, thanks so much for this tutorial. What might have taken me days to figure out took about ten minutes thanks to you. Kind regards, craigr

All the ping times are poor, but actual data transfer rates may not be effected by high ping times. Though higher ping times often indicate poor bandwidth volume. I would usually get less than 40-65 ms for Toronto. These were what I got: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping de-berlin.privateinternetaccess.com Pinging de-berlin.privateinternetaccess.com [193.176.86.134] with 32 bytes of data: Reply from 193.176.86.134: bytes=32 time=149ms TTL=54 Reply from 193.176.86.134: bytes=32 time=150ms TTL=54 Reply from 193.176.86.134: bytes=32 time=150ms TTL=54 Reply from 193.176.86.134: bytes=32 time=149ms TTL=54 Ping statistics for 193.176.86.134: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 149ms, Maximum = 150ms, Average = 149ms C:\Windows\system32>ping de-frankfurt.privateinternetaccess.com Pinging de-frankfurt.privateinternetaccess.com [185.220.70.163] with 32 bytes of data: Reply from 185.220.70.163: bytes=32 time=146ms TTL=54 Reply from 185.220.70.163: bytes=32 time=145ms TTL=54 Reply from 185.220.70.163: bytes=32 time=147ms TTL=54 Reply from 185.220.70.163: bytes=32 time=147ms TTL=54 Ping statistics for 185.220.70.163: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 145ms, Maximum = 147ms, Average = 146ms C:\Windows\system32>ping sweden.privateinternetaccess.com Pinging sweden.privateinternetaccess.com [45.12.220.246] with 32 bytes of data: Reply from 45.12.220.246: bytes=32 time=156ms TTL=55 Reply from 45.12.220.246: bytes=32 time=155ms TTL=55 Reply from 45.12.220.246: bytes=32 time=156ms TTL=55 Reply from 45.12.220.246: bytes=32 time=154ms TTL=55 Ping statistics for 45.12.220.246: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 154ms, Maximum = 156ms, Average = 155ms C:\Windows\system32>ping swiss.privateinternetaccess.com Pinging swiss.privateinternetaccess.com [185.212.170.184] with 32 bytes of data: Reply from 185.212.170.184: bytes=32 time=143ms TTL=55 Reply from 185.212.170.184: bytes=32 time=145ms TTL=55 Reply from 185.212.170.184: bytes=32 time=144ms TTL=55 Reply from 185.212.170.184: bytes=32 time=146ms TTL=55 Ping statistics for 185.212.170.184: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 143ms, Maximum = 146ms, Average = 144ms C:\Windows\system32>ping france.privateinternetaccess.com Pinging france.privateinternetaccess.com [194.99.106.148] with 32 bytes of data: Reply from 194.99.106.148: bytes=32 time=148ms TTL=52 Reply from 194.99.106.148: bytes=32 time=147ms TTL=52 Reply from 194.99.106.148: bytes=32 time=147ms TTL=52 Reply from 194.99.106.148: bytes=32 time=147ms TTL=52 Ping statistics for 194.99.106.148: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 147ms, Maximum = 148ms, Average = 147ms C:\Windows\system32>ping czech.privateinternetaccess.com Pinging czech.privateinternetaccess.com [185.216.35.68] with 32 bytes of data: Reply from 185.216.35.68: bytes=32 time=155ms TTL=55 Reply from 185.216.35.68: bytes=32 time=155ms TTL=55 Reply from 185.216.35.68: bytes=32 time=154ms TTL=55 Reply from 185.216.35.68: bytes=32 time=156ms TTL=55 Ping statistics for 185.216.35.68: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 154ms, Maximum = 156ms, Average = 155ms C:\Windows\system32>ping spain.privateinternetaccess.com Pinging spain.privateinternetaccess.com [185.230.124.50] with 32 bytes of data: Reply from 185.230.124.50: bytes=32 time=140ms TTL=56 Reply from 185.230.124.50: bytes=32 time=140ms TTL=56 Reply from 185.230.124.50: bytes=32 time=141ms TTL=56 Reply from 185.230.124.50: bytes=32 time=141ms TTL=56 Ping statistics for 185.230.124.50: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 140ms, Maximum = 141ms, Average = 140ms C:\Windows\system32>ping ro.privateinternetaccess.com Pinging ro.privateinternetaccess.com [185.210.218.108] with 32 bytes of data: Reply from 185.210.218.108: bytes=32 time=189ms TTL=50 Reply from 185.210.218.108: bytes=32 time=189ms TTL=50 Reply from 185.210.218.108: bytes=32 time=186ms TTL=50 Reply from 185.210.218.108: bytes=32 time=185ms TTL=50 Ping statistics for 185.210.218.108: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 185ms, Maximum = 189ms, Average = 187ms C:\Windows\system32>ping israel.privateinternetaccess.com Pinging israel.privateinternetaccess.com [31.168.172.142] with 32 bytes of data: Reply from 31.168.172.142: bytes=32 time=192ms TTL=55 Reply from 31.168.172.142: bytes=32 time=193ms TTL=55 Reply from 31.168.172.142: bytes=32 time=192ms TTL=55 Reply from 31.168.172.142: bytes=32 time=192ms TTL=55 Ping statistics for 31.168.172.142: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 192ms, Maximum = 193ms, Average = 192ms C:\Windows\system32> craigr

If you want to find which has the best speed than you just have to try them. Going back and forth across the pond will absolutely slow things down. I could usually get 8-10 MB/s off of Toronto. I tried over seas port forwarding in the past and always found speeds were deleteriously affected. I think we need to hope that port forwarding is returned to the Canadian servers quickly. Port forwarding isn't just about speed, it's about being able to find peers to upload to and download from. Without port forwarding most private trackers just won't work at all or possibly very poorly. Let's keep our fingers crossed. craigr

2020-04-09 11:33:21,842 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com Best regards, craigr

Yeah, this morning I awoke to no traffic and tried to reconnect to Toronto and Montreal... no go. Found the info Googling and Berlin is working for me. I came here to post this info, but you already had it up. Should have come here first. According to the logs my Toronto port forwarded connection was doped at 00:47 this morning and deluge continuously tried to reconnect for ten hours after that. Strange timing. It has been working fine until then. Weird because PIA support says it's been down for nine days. craigr

I've been using this plug in for a very long time and absolutely love it. Thanks so much! I have a request. Would it be possible to move the "IPMI Summary" on the Dashboard from the top of the page to the bottom of the page? With the newer look of unRAID the look and layout for the IPMI Summary just down't match and I'd also like to have access to other information at the top of the page. A silly cosmetic tweak I know, but I just thought I would ask. Kind regards, craigr

I am running binhex-delugevpn already. Is it possible to run binhex-SABnzbdVPN at the same time considering there would be two VPN connections from the same PC? Better yet, is it possible to simply use the same VPN connection that binhex-delugevpn is already using? Thanks for any help! Kind regards, craigr

Installed RC3 today and now can't access and of my DUNE players via SMB. Tried deleting and recreating the DUNE user and resetting permissions on the shares. Also checked SMB settings. Reverted back to 6.6.7 and everything works fine again. craigr

/Media_4K/Movies/movie name Like that? craigr

Could you please give me the exact syntax for that? Thanks again, craigr

And what's weird is that when I put in that path it continues to recheck in its default download directory.

Unfortunately not. I tried several variants based on your idea as well. This can't possibly be too hard right? Thanks, craigr

I've got a question on directories with spaces. I created a new path for Deluge to use with the following parameters: Config Type: Path Name: Host Path 4 Container Path: /Media_4K/Movies Host Path: /mnt/user/Media_4K/Movies/ Access Mode: Read Only Description: path for 4K movies When I complete a torrent I want to manually use "Move Download Folder" inside of Deluge. So I right click my torrent in Deluge, select move download folder, and then this in and all is well. /Media_4K/Movies/movie However, I cannot figure out how to do this if there is a space in the movie's name. For example, if the title is "movie name" and I try to use: /Media_4K/Movies/movie name than it fails and goes back to the default directory on the cache drive. I have also tried "/Media_4K/Movies/movie//name" and "/Media_4K/Movies// movie name" but neither work. I have also tried putting them in quotes, but when I do that Deluge makes a directory in appdata and copies it there. How do I do this most basic thing? Thanks! craigr

Is everyone having the unpacking stall issue or is this just a few people? I'm trying to decide if I want to install the plugin or not... Also, is there a way to use the VPN from your deluge plugin o cover your NZBGet plugin? Thanks as always and kind regards, craigr

Sorry if this has already been asked, but is it possible to use "binhex sabnzbdvpn" and "binhex delugevpn" at the same time? I ask because it seems like there would be a problem with two VPN connections on on computer at the same time? Is there a way for one docker to use the VPN service from the other? Thanks as always, craigr

Updated with no issues. Thanks, craigr

Thanks clowrym for this Transmission docker. I'm having issues with Deluge and wanted to try something different. Apparently Deluge can start to have issues when you are seeding more than around 100 torrents... Anyway, your Transmission was simple to setup with PIA and I am getting an IP in Toronto with port forwarding. I read several pages of this thread, but didn't see an answer; does your Transmission docker have a kill switch? I see this under "open VPN options" "--inactive 3600 --ping 10 --ping-exit 60 --restart=always" what exactly does each mean? Should I add the --restart=always? Best, craigr

Updated without any issues. Thanks, craigr

I've been trying to figure this out for two days... Can I get Linuxserver.io - The-Lounge to connect through a proxy server. Most notably, I have binhex - DelugeVPN running along with his Privoxy. How do I configure The-Lounge to send traffic through my proxy server? I'm pulling what's left of my hair out!!! Thanks to anyone who can help. Kind regards, craigr

Sorry, maybe an obvious question, but not to me. Is privoxy built into your deluge, Shout-IRC, or unRAID? It sounds like a perfect solution, but I have never used it before... Thanks and kind regards, craigr

Is there any way to make the VPN connection in binhex - DelugeVPN cover the entire server instead of just Deluge? More specifically, I would like to have the VPN tunnel also cover the Linux|Server Shout-IRC docker. I know there are dockers and plugins that can be installed to cover the whole server, but they don't have a kill switch the way that binhex - DelugeVPN does and I don't want that to ever be exposed. Thanks, craigr

Been thinking of switching to Tomato and after this I may do so. The newest Kong dd-wrt for my R7000 is 7 months old and caused these issues... seems Kong has lost interest. best, craigr

At least I did check to make sure my router was plugged in 😜 craigr

Something is broken in the newest DD-WRT firmware for my R7000 because the command to renew the DHCP lease from the U-Verse junk hardware no longer was allowing the lease to renew without resetting the WAN connection. So every 10 minutes my DHCP lease was expiring and forcing a new connection. I really wish ATT would sell just a damn modem and not an entire access point with modem and wifi router... especially one that can't totally be bridged and also requires that the DHCP lease expires every 10 minutes when your real router is in DMZ+... sigh, it's always something. Anyway, old firmware on my DD-WRT router solved the problem. Blah blah blah... Thanks for having me look back that way again when I thought it was already covered craigr

There was also an update to Deluge the other day as well... That may have been when the trouble started. craigr