neardeaf

Would you mind going into detail about how to set this up? Do we just put our openvpn files in the /openvpn directory with each different endpoint as a subdirectory? Thanks

I'm in the process of redoing my sabnzbdvpn setup and run into the same issue. Isolated slow speeds all the way down to using a mullvad wireguard .conf file. The logs also show things moving slowly. Direct unpack takes forever, etc. I have a very fast server so it's down to this one thing and it's driving me crazy

Ahh okay that might me the solution I need then, but I'd like to try and give it a shot to see if I can get something working and maybe submit my first PR or something!

Thanks a ton @binhex for the fantastic work on this image. I was a faithful Mullvad user until they killed off Port Forwarding, so I switched to ProtonVPN and was immediately inconvenienced by the dynamically changing port forward number, which you brilliantly solved! I have a question regarding the reliance on the wg0.conf file located in /config/wireguard/. I used to use this container with an OpenVPN config that had a similar method using .ovpn files, but ultimately switched away because I got irritated at trying to login to the WebUI on my local network to find that I couldn't connect to it because the specific endpoint I was routed to was down, thus needing to take 20 minutes to obtain new config files and rebuild the container. It wasn't the worst thing ever but I didn't have any sort of watchdog notification system to alert me that my client was down for multiple days Am I going to run into the same issue here? If so, any ideas on how to be proactive about this setup? I'm not sure if ProtonVPN's website would allow me to try and write a program to curl to the downloads page and grab a different wireguard conf download, rename/replace the existing wg0.conf and restart the container. Would be uncharted (but interesting) territory for me.