Omada OpenVPN client not connect to software OpenVPN server (on windows Server 2022) - [SOLVED]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada OpenVPN client not connect to software OpenVPN server (on windows Server 2022) - [SOLVED]
Tags:
#VPN
#OpenVPN
#Highlighted Thread
Hi
Sorry for my bad English
Has anyone managed to configure the Omada OpenVPN client (software controller on linux) connect to a server with openvpn (server mode) installed?
I have Windows Server 2022 in the cloud with OpenVPN running in server mode (Certificate-based configuration).
I prepared a *.ovpn file to contain certificates (<ca>, <cert>, <key> sections) and uploaded it to the Omada controller.
The same file uploaded to the OpenVPN software client works and connects.
TP-link does not connect from Omada. I don't even try, because there is nothing in the OpenVPN server logs. I tried downgrading the OpenVPN version on the server from 3.x to 2.4. This still didn't help.
Example of my *.ovpn configuration:
----- client dev tun proto udp remote 145.xxx.xxx.xxx 1194 resolv-retry infinite nobind persist-key persist-tun remote-cert-tls server cipher AES-256-GCM connect-retry-max 25 verb 3 [cacert] -----BEGIN CERTIFICATE----- MIIE4DCCA8igAwIBAgIUA5SFtn4j4P7NPea2Nrk1mZ2CTFYwDQYJKoZIhvcNAQEL ... 7kOFSw== -----END CERTIFICATE----- [cacert] [cert] -----BEGIN CERTIFICATE----- MIIFITCCBAmgAwIBAgIBAjANBgkqhkiG9w0BAQsFADCBnjELMAkGA1UEBhMCUEwx .... GBmPXSZcXkaKIaD3kIOlJi4BYADU -----END CERTIFICATE----- [cert] [key] -----BEGIN PRIVATE KEY----- MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQClNn5d5g4EXv/2 ... sm/CxPdywek0R9si8qAcG9Q= -----END PRIVATE KEY----- [key]
I had to replace "<>" and chance ca_to_cacert in the sertificate sections because the forum framework wouldn't go through
1 Accepted Solution