Thu Mar 18, 2021 11:21 am
OK. So two points.
First, the certificate you set in the /interface ovpn-client configuration must be the one authenticating your client to the server, which is the one for which you have the private key, i.e. the dyn05-10-8-0-75.ovpn_1 one.
Second, under normal circumstances, you should not need the server certificate itself - instead, you should use the certificate of the authority that has signed it. But the ..._0 certificate is not one of an authority, so it seems to be the one of the server itself. But I am not sure whether Mikrotik's OpenVPN implementation supports server authentication by the server's certificate alone, without having the certificate of the issuing authority. So if the connection still fails after you start using the proper certificate for the client as explained above, the error message should be different. If that is the case, switching off verify-server-certificate could be a way to check this, but not a recommended setting for actual use of the VPN, as without the certificate check, your connection could be redirected to some other server impersonating the real one.
So until the connection finally succeeds, uncheck add-default-route, but that doesn't prevent the username and password from leaking to the rogue server.