mirkotik openvpn

[totza]

Hello,

I have vpn server set on mikrotik v.6.49.10. CA CRL host is set by DNS name of router, because my IP from provider is dynamic.
Vpn server work great, until last week. I had to create new ca, client and server again, because my internet provider decided to switch from static to dynamic IP.
When I try to connect from android with official app, version 3.3.4, I get this message - peer certificate verification failure openvpn


Log file:
VERIFY FAIL: depth=0, signature: RSA-SHA256 [unsupported certificate purpose]
Transport Error: OpenSSLContext:SSL::read_cleartext: BIO_read failed, cap=2576 status=-1: error:1416F086:SSL routines:tis_proce ss_server_certificate:certificate verify failed


EVENT: CERT_VERIFY_FAIL
info='OpenSSLContext:SSL::read_cleartext: BIO_read failed, cap=2576 status=-1: error:1416F086:SSL routines:tls_proce Ss_server_certificate:certificate verify failed'

I'm attaching my client config file.

##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
cipher AES-256-CBC

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
proto tcp
;proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote mikrotik dns 443

# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
;ca ca.crt
;cert client.crt
;key client.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# This is an important precaution to protect against
# a potential attack discussed here:
# http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the keyUsage set to
# digitalSignature, keyEncipherment
# and the extendedKeyUsage to
# serverAuth
# EasyRSA can do this for you.
remote-cert-tls server
;ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
;data-ciphers AES-256-CBC
;data-ciphers-fallback 'AES-256-CBC'

cipher AES-256-CBC
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
#comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

<ca>
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
</ca>


<cert>
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
</cert>

<key>
-----BEGIN ENCRYPTED PRIVATE KEY-----
-----END ENCRYPTED PRIVATE KEY-----
</key>

<auth-user-pass>
user name
password
</auth-user-pass>

auth-nocache
redirect-gateway def1

dhcp-option DNS IP
register-dns
block-outside-dns

[openvpn_inc]

Hello,

> peer certificate verification failure

Yeah this basically means that there is something wrong with the provided CA and certificates. They don't appear to match up, therefore verification of the identity of the server and/or client cannot proceed. So once you fix that problem with your certificates, the issue should be resolved.

Kind regards,
Johan