Hello,
I have a problem where I can successfully add a magnet link but no peers connect. I’m using OpenVPN through Private Internet access. I can add torrent files and they add and download no problem but the magnet links won’t start connecting to peers. I stopped VPN readded the magnet link and it works. What could be causing magnet links to not work when connected through VPN?
Thanks.
rpi2 - dietpi v100
Are you forwarding internet traffic through your private VPN server?
Can you show me the /etc/openvpn/server.conf and your client connection file (hide any personal info and unified keys).
I don’t have a server.conf this was a self install openvpn and it was installed prior to v100.
Here’s the contents of /etc/openvpn
root@dietpi:/etc/openvpn# dir -l
total 36
-rw-r--r-- 1 root root 1395 Oct 23 22:44 ca.crt
-rw-r--r-- 1 root root 577 Oct 23 22:44 crl.pem
-rwxrwxrwx 1 root root 94 Oct 23 22:46 down.sh
-rwxrwxrwx 1 root root 20 Oct 23 22:48 login.conf
drwxr-xr-x 2 root root 4096 Oct 23 22:42 pia
-rwxrwxrwx 1 root root 95 Oct 23 22:45 route-up.sh
-rwxr-xr-x 1 root root 1301 Dec 5 2014 update-resolv-conf
-rwxrwxrwx 1 root root 356 Oct 23 22:47 USEast.conf
-rwxrwxrwx 1 root root 363 Oct 23 22:47 USNYC.conf
Here’s the the config file where open vpn connects to.
client
dev tun
proto udp
remote us-newyorkcity.privateinternetaccess.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca /etc/openvpn/ca.crt
tls-client
remote-cert-tls server
auth-user-pass /etc/openvpn/login.conf
comp-lzo
verb 1
reneg-sec 0
crl-verify /etc/openvpn/crl.pem
daemon
route-up /etc/openvpn/route-up.sh
down-pre
down /etc/openvpn/down.sh
Would it be worth doing the install through dietpi? Does the integrated install offer any connection redundancy if the VPN were to drop for whatever reason it reconnects?
It may be in one of the following files:
USEast.conf
USNYC.conf
Would it be worth doing the install through dietpi? Does the integrated install offer any connection redundancy if the VPN were to drop for whatever reason it reconnects?
A reconnect method must be completed at the client end, regardless of DietPi OpenVPN installation or not. Whether thats a .bat script, system service that monitors the state, or additional software.
It may be in one of the following files:
USEast.conf
USNYC.conf
Yea that’s what I posted above for the config file. I still have the same issue do you see any settings that may seem off in the conf file? Is there another spot I might need to check?
I’ll look into the reconnect issue separately.
The file you posted is the client file. Its a bit messy, however, you can compare your files with what DietPi uses:
server = DietPi/dietpi/dietpi-software at master · Fourdee/DietPi · GitHub
client = DietPi/dietpi/dietpi-software at master · Fourdee/DietPi · GitHub
As your VPN server is not on a DietPi system (http://privateinternetaccess.com), i am unable to offer you further support.
I would suggest you contact your VPN provider http://privateinternetaccess.com for support.