-
Since #2596 was open by a different user, was closed, and the user did not give clear details, I would like to continue the discussion here in a new discussion. There are some issues with ProtonVPN that need to be worked through that I need some help with. ProtonVPN doesn't tell you your port forward. You have to use natpmpc to set up port mappings. https://protonvpn.com/support/port-forwarding-manual-setup/ The first step is to run...
...to update the package list and install natpmpc. This only has to be run once upon docker creation. Then you need to run This needs to be run every 60 seconds. Sample output can be seen on ProtonVPN's website. The magical grep setup to cull the port forward port is I lifted that and cleaned it up from here: https://www.reddit.com/r/ProtonVPN/comments/10n0w0m/port_forwarding_on_debiadietpi_with_wireguard/ However, what I need to figure out is...
Right now, I'm manually having to update the port number, and that gets really annoying. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
Hmm... So that gives me some options, especially with the In writing the response to you, @edgd1er , I found something useful. This script is tantalizingly close to what I need as it doesn't need to bring down Transmission. It only needs remote access to update the port setting. https://github.com/haugene/vpn-configs-contrib/blob/main/openvpn/pia/update-port.sh However, I can't seem to get past the login for transmission-remote.
That translates to...
Giving me the edit: It's because my password is hashed. Not sure how I can use this method if the password is hashed. |
Beta Was this translation helpful? Give feedback.
This is what I got working...
It's not pretty, and I settled on running it as a task on my Synology (
docker exec
), but it works for now.I'll open another question regarding the transmission-remote and passwords.