JOSEPH ENGELMANN

This method worked for me as well! thank you.

thank you.

has anyone gotten this to work with a dedicated ip assigned by the vpn provider? i have gone over the provider's doc's and the vpn.md for docker container but for some reason i have no idea why it won't use the dedicated ip, i have tried to change the "remote" domain "ca-toronto.privacy.network 1197" for example to the ip i was assigned, still have the auth-user-pass.conf in there and it fails to connect and therefore also doesn't finish the startup for the container when the ip is used. here is the the main part of the config file if anyone has any idea how to specify how the container connects and to what ip, that would be great. client dev tun proto udp remote ca-toronto.privacy.network 1197 "Tried to change this to the ip of the dedicated ip i was assigned without success" resolv-retry infinite nobind persist-key persist-tun cipher aes-256-cbc auth sha256 tls-client remote-cert-tls server auth-user-pass compress verb 1 reneg-sec 0

if your using a reverse proxy, then i have found that if you use the address you set up in that it works just fine, i had to do the same thing, though i am using it to access the unraid-ui as well, so if you have "unraid.yourproxiedaddress.com" to access your unraid, then that is the address you would need to use for your base url in the grafana panel's settings, not an ip address, i believe it has to do with internal translations of ip's to dns.