@travelmore said in OpenVPN not connecting:
to other, whereas in that link the person mentioned changing it to Interface IP address instead of other.
Be careful with this :
cba53f1e-fee1-42d5-8f76-215842ebfc49-image.png
as that a hostname like (RFC1918 like 192.168.0.b) this will be wrong in 99,x % of all cases.
When you are out, somewhere in the wild, surround by the hostile Internet, and you want to connect to 'home' over VPN, you have to connect to your ISP WAN IPv4. Certainly not to your RFC1918 like 192.168.0.x as shown in the image above, which can't be routed over the net.
So : second best choice : the ISP WAN as a host name.
Host name is your tunnel end point, and as the comment says : it could be an IP or a host name. If you shose the latter, it should be resolvable there where you are now. Said differently : it should be resolvable anywhere on the internet.
So : best : set up a DYNDNS so that a known 'hostname' always points to your ISP WAN. This is valid and useful if you have a dynamic IP and/or a static WAN IP.