Closed dustinleblanc closed 10 months ago
Thanks for grabbing those container logs!
Unfortunately, this appears to be an issue with the VPN container itself since this repo does not directly modify any openvpn files, but you were definitely on the right track for troubleshooting.
ProtonVPN is considered an "External Provider" and I haven't dealt with one of these before, but I did some digging and found that how to configure this external ProtonVPN provider can be found here: https://github.com/haugene/vpn-configs-contrib/tree/main/openvpn/protonvpn
With that said though, the below may resolve your issue.
If you're using the "basic" configuration, can you edit your vars/custom/transmission.yml
file to add the following to the bottom:
transmission_additional_env_vars:
{
"OPENVPN_CONFIG": "us.protonvpn.net.udp"
"TRANSMISSION_DOWNLOAD_QUEUE_SIZE": "25",
"TRANSMISSION_MAX_PEERS_GLOBAL": "3000",
"TRANSMISSION_PEER_LIMIT_GLOBAL": "3000",
"TRANSMISSION_PEER_LIMIT_PER_TORRENT": "300",
}
If you're using the advanced configuration, could you try adding the below environment variable to the transmission_additional_env_vars
list in the vars/custom/transmission.yml
file?
"OPENVPN_CONFIG": "us.protonvpn.net.udp"
If you need to select a different country other than US, check out the configuration page at the link above for the available configs.
I actually just realized that PR https://github.com/ahembree/ansible-hms-docker/pull/41 helps fix this, I'll dig deeper into merging those proposed changes.
Thanks so much for the quick response, giving it a try!
I'm having issues getting that syntax to parse in the yaml interpreter (using the basic config btw). I'll keep trying but just a heads up
Oh whoops I forgot a comma at the end of a line, so it should be:
transmission_additional_env_vars:
{
"OPENVPN_CONFIG": "us.protonvpn.net.udp",
"TRANSMISSION_DOWNLOAD_QUEUE_SIZE": "25",
"TRANSMISSION_MAX_PEERS_GLOBAL": "3000",
"TRANSMISSION_PEER_LIMIT_GLOBAL": "3000",
"TRANSMISSION_PEER_LIMIT_PER_TORRENT": "300",
}
sorry about that
No problem, thanks again for such a quick response
PLAY RECAP **************************************************************************************************************************************************
localhost : ok=29 changed=2 unreachable=0 failed=0 skipped=63 rescued=0 ignored=0
Looks like the whole playbook ran now, so time to go check it out and play :)
Thank you again, have a great weekend!
Thanks for checking out and using my repo, hopefully it works well and fits your needs!
Any feature recommendations or enhancements to initial setup steps are always welcome.
If you encounter any further issues, don't hesitate to create another issue.
Just trying to get setup on a fresh install of Ubuntu server, ran into this:
if I inspect the logs, this is what I see:
I wanted to try to troubleshoot this myself but I don't know enough about OVPN and transmission in a container to know what I am doing. My setup is just an old tower setup with Ubuntu server (22.04) and for the VPN I am using the credentials from my proton VPN OVPN credentials. I've tried this both by modifying the config to run ansible remotely from my laptop, and by running ansible directly on server (which seems to be the project intention) I am running the script as root as the make file doesn't seem setup to run via become, etc. I have suspicion that there might be some ovpn config I can tweak here but I am not sure.