Since I'm a firm believer of leaving behind the steps I needed to help others: I wound up with the following script I adapted and put on a cronjob to check every 2 hours. Seems to be working! #!/usr/bin/env bash # Author: PanoramicPanda # Based on https://github.com/HTPCGuides/pia-port-forwarding-sc...

Okay, update: In ifconfig under tun0, there's an row for inet: 10.23.xx.xxx. I used that instead of "tun0" or the IP PIA gives me (172.98.xx.xxx) and downloads started working! Test active port also gives me a checkmark! The IP at the bottom of deluge is also the IP that PIA shows me as. T...

I do indeed have tun0, and after restarting deluged it does not work. A ncat -l <port> test did spit me out information, so it seems to be port forwarding correctly. Just can't see it from yougetsignal for some reason, so maybe that's the issue maybe it's not. 😔 Tried setting them to the IP directly...

Setting listen_interface and outgoing_interface to "tun0" (which is PIA's OpenVPN interface according to `ifconfig`), makes my torrents not do anything. No downloading, no seeding. "Port Issue" in lower right corner, "N/A" for IP at bottom. Incoming port is set to PIA's...

I'm a complete Linux noob but have managed to stumble my own way through the Docs to set up Deluged as a service on the Pi, and I'm able to connect to it from the interface on my Windows machine. It listens to folders for files, and even copies completed downloads to my NAS. Huzzah! However, regardi...