jleiss

I had issues with Vancouver yesterday, switched to Toronto and got that speeds I expected to get.

Thank you, it's a proxmox server and they are only at 5.4 for now, might be awhile before they get there. Unless I find a workaround i'll stick with openvpn.

updated as requested with same errors, supervisord log attached. UN & password cleared. supervisord.log

I did except for trying to change the endpoint, I will do that now.

not sure the security of the public and private key so I have XXXX those out, here is what the config file looks like [Interface] Address = 10.27.139.48 PrivateKey = XXXXXXXXXXXXXX PostUp = '/root/wireguardup.sh' PostDown = '/root/wireguarddown.sh' [Peer] PublicKey = XXXXXXXXXXXXXXXXXXX AllowedIPs = 0.0.0.0/0 Endpoint = nl-amsterdam.privacy.network:1337

using the default wireguard config that comes from deployment, no modifications to it. Is this similar to openvpn and I need to get a wireguard config from PIA?

I tried also.. getting warnings about the wireguard config being world accessible and errors bringing up the wireguard interface 2020-10-12 20:24:13,996 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2020-10-12 20:24:14,002 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2020-10-12 20:24:14,006 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2020-10-12 20:24:14,008 DEBG 'start-script' stderr output: Error: Unknown device type. 2020-10-12 20:24:14,010 DEBG 'start-script' stderr output: Unable to access interface: Protocol not supported 2020-10-12 20:24:14,010 DEBG 'start-script' stderr output: [#] ip link delete dev wg0 2020-10-12 20:24:14,013 DEBG 'start-script' stderr output: Cannot find device "wg0" 2020-10-12 20:24:14,013 DEBG 'start-script' stdout output: [warn] WireGuard interface failed to come 'up', exit code is '1'

there is also a limit on number of remote lines in a config file, you will only be able to add like 50 or so. BinHex- is there a set a bittorrent port range with your docker instead of it being randomly assigned? I tried setting it in the qb config file but it ignores that.

yes, using the arch-qbittorrent found here: https://hub.docker.com/r/binhex/arch-qbittorrentvpn/

greatly appreciate you taking this on.. the current containers out there are lacking. I had some issues with getting this container up but I do see it's a new build so some adjustments are likely needed. Here's some of the things I encountered. 1. vpn wouldn't connect intially because it couldn't load iptable_mangle was able to work around this by adding --cap-add=NET_ADMIN --device=/dev/net/tun (running proxvox which is Debian 9.6 underneath) 2. couldn't get Privoxy to start, getting permission denied errors. default permissions on this folder is d----w--w- 2 nobody users 2 Nov 14 15:37 privoxy under default deployment nothing is getting copied to /config/privoxy/ because of permission issues.. if I modify the permissions manually I can see that files are copied to that folder. Still doesn't autostart but I am able to start it manually based on the command line from your script. 3. getting errors reading files created by script, for example /home/nobody/getvpnextip.sh: line 9: /home/nobody/vpn_external_ip.txt: Permission denied. These files have the same permission as privoxy. qbittororrent doesn't auto start for me yet, but I am able to kick it off manually. 4. Once into qbittorrent I can see that in the settings the download folder is not populated with /data which is the default location you provided for the download folder. Just a few things I have noticed so far.. more than willing to be a guinea pig to work things out.

Hello MarkusMcNugen, I current use delugevpn, but I've anxiously been waiting for a qbittorrent/openvpn combination that will work for me as that is my torrent client of choice. I saw that you recently updated your build and was going to try it, but I am getting the following error when trying to pull down the container: docker: Error response from daemon: pull access denied for v, repository does not exist or may require 'docker login'. I provided my docker creds and tried to pull it down but it didn't change anything.