[[Support] binhex - DelugeVPN]

Yes see my post above.  It's required to give the -e flag, as it ignores whats in your ovpn file and overwrites it.  If you leave it blank, you will give an error.  I was proposing allowing us to manage it with the ovpn file so I don't have to keep rebuilding my docker containers if I want to use a different exit point with my provider.  I'll probably just roll my own.

 

I'm trying to set up with a custom openvpn.ovpn configuration but find that it keeps being overwritten.  From the logs:

 

   Env vars defined via docker -e flags for remote host, port and protocol, writing values to ovpn file...

 

If I remove these variables then I get the following error instead:

 

   [crit] VPN provider remote gateway not defined (via -e VPN_REMOTE), exiting...

 

If I set them to blank it still happens.  Any clues as to what's going wrong here?

[[Support] binhex - DelugeVPN]

Is there any way to adjust the start.sh script to not exit if the VPN remote is defined in the openvpn.ovpn file? i.e. right now it's:

 

        if [[ ! -z "${VPN_REMOTE}" ]]; then

                echo "[info] VPN provider remote gateway defined as ${VPN_REMOTE}"

        else

                echo "[crit] VPN provider remote gateway not defined (via -e VPN_REMOTE), exiting..." && exit 1

        fi

 

Maybe instead, grab variables from these lines in the ovpn file if they exist, for example, excerpt from AirVpn ovpn file:

 

proto udp

remote america.vpn.airdns.org 443

 

So something like after the "else"

 

else

    ${VPN_REMOTE} = `grep remote ${VPN_CONFIG} | awk '{print $2}'`

    ${VPN_PORT} = `grep remote ${VPN_CONFIG} | awk '{print $3}'`

    ${VPN_PROTOCOL} = `grep proto ${VPN_CONFIG} | awk '{print $2}'`

 

?