OpenVPN Support Forum

It happens sometimes that my dynDNS is not working. My provider dooesn't change my IP too often, so it would bea good idea to connect via IP in such cases. Like today.

My config.ovpn contains
remote 90.146.xxx.xxx 1194

But in the logfile there is following error message:
2022-09-29 09:26:02 RESOLVE: Cannot resolve host address: blablabla.synology.me:1194 (Der angegebene Host ist unbekannt. )

I double checked if I changed the right config file. Why does openVPN not use 90.146.xxx.xxx but the (today invalid) dynDNS?

Hello mpunktw,

You submitted this in OpenVPN Connect for Windows forum so I must assume you are using OpenVPN Connect v3 on Windows. In that case, you need to make the change in the config.ovpn file, and reimport that file so it will take effect.

However there is an easier way, and maybe you have already been using this. If you tap the pencil icon to edit the profile, you can see a 'Server Override (optional)' field. You can put an entry in here like 90.146.xxx.xxx so that it will override whatever was configured in the OpenVPN configuration profile itself. This is for situations like these where your server address changed and you need to update it without having to edit the configuration profile.

Kind regards,
Johan

Thank you for the quick reply.
I'm using openVPN 2.5.7. which i dowloaded from here: https://openvpn.net/community-downloads/ a few minutes ago.
When right click > import > file openVPN says that the config is already in use.
I cannot find a pencil icon in this version

Hello mpunktw,

Yeah you posted in the wrong section because that is not OpenVPN Connect, that is OpenVPN GUI, the community client. Everything I said earlier then does not apply.

In your case you will have to stop the connection first, and then edit the config file, and then start the connection again. If that doesn't work try a reboot of your Windows machine. If that doesn't work, then I would say you're not using that config file or that config file has more remote lines in it that still reference the domain instead of the IP.

Good luck,
Johan