On 02/18/17 23:37, InvalidPath wrote: > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: VERIFY ERROR: > depth=0, error=certificate signature failure: C=US, ST=MT, > O=$organization, OU=Operations, CN=xxxx-v > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: OpenSSL: > error:14090086:SSL routines:ssl3_get_server_certificate:certificate > verify failed > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: TLS_ERROR: BIO > read tls_read_plaintext error > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: TLS Error: TLS > object -> incoming plaintext read error > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: TLS Error: TLS > handshake failed > Feb 18 08:32:16 localhost.localdomain nm-openvpn[7769]: > SIGUSR1[soft,tls-error] received, process restarting > > Which is even more confusing because this config file works perfectly > with the Windows OpenVPN client. So there must be some difference in > how the clients use this file because teh certificate is valid. I did > goto the link in this error log and it's really not much help since > the server certificate and actually the entire config was generated > from pfSense. This does appear to be the root of the problem. That is, problem with the certs. Sorry, without knowing who the VPN Provider is and without having an actual test case with real information to work with it would just be a guessing game for me. I'm not particularly fond of guessing games. -- Fedora Users List - The place to go to get others to do the work for you _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
