PeterB

Since PIA no longer support L2TP for my router, I'm still looking for alternative VPN providers. PureVPN appear to have strong support for L2TP, but I read here of people having issues with DelugeVPN/PureVPN. Does anyone have this working satisfactorily, perhaps with their port-forwarding add-on?

Here's an interesting thought .... Part of the reason for urgent replacement of parity drives is that my Parity2 drive appears to have failed. The parity drive which has failed (a relatively new drive), and this new drive which has failed Preclear are both on the same SATA disk interface card - a two port generic Asmedia device, purchased from China. Perhaps the issue is with the SATA interface? I think I should try moving both of these drives to other SATA ports.

So, is there any way I can determine what caused the failure? Do I just re-run the Preclear? The other drive is still running the Post-Read, at 58%.

I am running preclear (gfjardim's plugin) to test two new drives for use as parity drives. One of the drives has just produced this: ############################################################################################################################ # # # unRAID Server Preclear of disk V9GXAXWL # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [8:28:17 @ 196 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [8:11:26 @ 203 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 19:58:40 | Total elapsed time: 19:58:40 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 194-Temperature_Celsius 39 - # # 196-Reallocated_Event_Count 0 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: Post-Read verification failed. Your drive is not zeroed. Is the system log the only way to get any more information about the failure? I attach extracts from the system log file for all the relevant entries I can find. PreclearLogEntries

Not for me. I leech to a cache-only share and seed from the array.

That makes sense. Since the first stage of my storage extension involves replacing the parity drives, I have ordered two 6TB Red Pro drives. I will consider further when the time comes to procure new data drives.

I download to a cache-only share, then allow deluge to move the files to another share, automatically, on download completion. No extra script needed. Check out deluge 'Preferences' -> 'Downloads', "Move completed to:"

I'm only running it as a thin client, so I wouldn't be aware. However, I'm not sure what issue you're referring to - I'm not aware of that problem on DelugeVPN. How would I identify it?

I think this was the prompt I was looking for! My router has four WAN ports, but only one connection is un-metered. I'd been trying to work out how to configure a route so that delugeVPN traffic only went to the un-metered port. I've just set a route for all traffic to a 1337 destination port to go via WAN2 and that seems to be working.

There are already later builds of Deluge, but not in the ArchLinux repositories. I'm running v2.1.1 on my desktop.

So there is nothing in the 'Repository:' field other than "binhex/arch-delugevpn"? And you've created the 'Wireguard:' field?

Errr... No, the other way round. privateinternetaccess.com are the legacy servers. privacy.network are the NewGen servers.

There are still some Legacy servers running - I'm using one with my router (which doesn't support OVPN or Wireguard). The list of available servers can be seen here (if you click 'Legacy'): https://www.privateinternetaccess.com/pages/network/

Thank you, sir!

My Internet connection went down for six hours. When it came back, DelugeVPN didn't re-establish the VPN automatically. On restarting the container, the VPN came up quickly and started transferring data again. The log file shows lots of repeated: 2020-10-23 09:32:19,037 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2020-10-23 09:32:19,061 DEBG 'watchdog-script' stdout output: [warn] VPN IP not detected, VPN tunnel maybe down 2020-10-23 09:32:21,053 DEBG 'start-script' stdout output: [info] Sending 'down' command to WireGuard due to dns failure... [info] Attempting to bring WireGuard interface 'down'... 2020-10-23 09:32:21,068 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2020-10-23 09:32:21,071 DEBG 'start-script' stderr output: wg-quick: `wg0' is not a WireGuard interface 2020-10-23 09:32:21,071 DEBG 'start-script' stdout output: [info] WireGuard interface stopped 2020-10-23 09:33:44,203 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... 2020-10-23 09:33:44,227 DEBG 'watchdog-script' stdout output: [warn] VPN IP not detected, VPN tunnel maybe down 2020-10-23 09:33:51,077 DEBG 'start-script' stdout output: [info] Sending 'down' command to WireGuard due to dns failure... 2020-10-23 09:33:51,077 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'down'... 2020-10-23 09:33:51,092 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2020-10-23 09:33:51,094 DEBG 'start-script' stderr output: wg-quick: `wg0' is not a WireGuard interface 2020-10-23 09:33:51,095 DEBG 'start-script' stdout output: [info] WireGuard interface stopped

I have never managed to achieve an encrypted connection - it always reverts to bare L2TP. PIA support aren't interested in resolving the issue. Express, on the other hand, happily negotiates IPsec. The PIA guide contains this sentence: "If you need encryption, please use the Private Internet Application or OpenVPN protocol with our service." suggesting that they are aware that IPsec doesn't work on an L2TP connection.

Yes, some locations have already been taken down. I use L2TP on my router so that I can selectively route traffic through the VPN - the location I was using, Chicago, has gone down today. I have switched to us-east which still seems to be operating .... but for how long? It looks like I will have to subscribe to two different VPN providers - one which supports port forwarding and one which supports L2TP. PIA have never supported L2TP/IPsec, so at least I have the option of finding a provider which offers that - such as ExpressVPN.

I need to add more capacity to my server and replace a failed drive. Most of my current drives are WD Red 3TB. My first step will be to replace the two parity drives with 6TB devices. I'm concerned about the performance aspects of the new 'shingled' drives. Should I simply move to WD Red Pro drives, or is there another recommended brand/model?

I've just started using this CUPS docker in order to print from a machine which has a very limited range of print drivers. Even though all my printers are networked (I wrote an lpr/lpd driver for it), the machine in question can only print to HP PCL, PS and a couple of other old protocols. This docker allows me to throw a PDF into a shared directory, and have it printed on, for instance, IPP ink jets.

I'm running 6.8.3. It seems perverse, to me, that when on the GUI dashboard, menu over a docker container offers an 'Update' option when there is no notified update. As soon as an update is notified for a particular container, the 'Update' option disappears. In other words, you can update a container as long as there is no update! Is there a good reason for this?

france.privacy.network is not the same as france.privateinternetaccess.com. As Binhex says, you don't appear to be running a current image, correctly set for the newgen servers.

Successfully switched from NewGen OVPN to Wireguard on PIA. All running without any apparent issues.

My DelugeVPN has been doing this for the last three hours: 2020-10-07 16:02:16,782 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 16:05:31,503 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 16:05:34,161 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 16:06:16,034 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 16:17:17,602 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 16:20:32,324 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 16:20:34,978 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 16:21:16,850 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 16:32:18,421 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 16:35:33,138 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 16:35:35,798 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 16:36:17,667 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 16:47:19,256 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 16:50:33,955 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 16:50:36,615 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 16:51:18,482 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 17:02:20,073 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 17:05:34,772 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 17:05:37,429 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 17:06:19,297 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 17:17:20,889 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 17:20:35,589 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 17:20:38,263 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 17:21:20,115 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 17:32:21,705 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 17:35:36,427 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 17:35:39,081 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 17:36:20,935 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 17:47:22,523 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 17:50:37,245 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 17:50:39,898 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 17:51:21,753 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 18:02:23,340 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 18:05:38,065 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 18:05:40,714 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 18:06:22,572 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 18:17:24,155 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 18:20:38,880 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 18:20:41,532 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' 2020-10-07 18:21:23,391 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '50478' 2020-10-07 18:32:24,973 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '33685' 2020-10-07 18:35:39,698 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '59422' 2020-10-07 18:35:42,350 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34056' What's going on? Edit to add: Restart seems to have fixed it for now.

Thin client works fine - your problem is Microsoft or Apple! Just thinking obliquely - if you were to set up a VM running Linux, could run the thin client on it with a remote desktop.

This doesn't seem to work for me. My DelugeVPN docker is currently configured with Google name servers. If I change the Key9 setting to two of the 10.0.0.? addresses, the vpn tunnel fails to come up. Have I misunderstood? 10.0.0.0/8 are private addresses so can't possibly work before the tunnel is up. Edit: Yep, I've just read again - those DNS addresses are for use within the PIA applications, and are set automatically.