Explain how to fix update-resolv-conf errors

[gpoole]

Documents a solution for the following error when using pre-made config files downloaded from VPN providers:

--up script fails with '/etc/openvpn/update-resolv-conf': No such file or directory

I have seen two major VPN providers include a baked in reference to this script in their downloadable configs and they assume that it's kicking in to update your DNS after the connection is established, so it's helpful for users with those configs to know how to fix the problem.

Thanks to @mil1i for the fix.

Related issues:
#90
#344
#271

[TBG-FR]

Thanks a lot for that hint ! Starting the script with the -d option is exactly what I needed to replace --up /etc/openvpn/update-resolv-conf --down /etc/openvpn/update-resolv-conf (moving from testing on my debian to a alpine docker)

However I have a message saying NOTE: unable to redirect default gateway -- VPN gateway parameter (--route-gateway or --ifconfig) is missing whereas when using update-resolv-conf I have a message saying /etc/openvpn/update-resolv-conf tap0 1500 1586 init (but in this case I run openvpn with --script-security 2, is it possible to do the same with the script ?)
Nevermind, using -D fixed that particular case.

If that can help somebody, using my config I also need to do a dhclient interface_name (e.g. dhclient tap0) after enabling VPN, to get an IPv4 address 😉