(OV10 Terra) A specific AP cannot be registered to OV Terra, as it remains in the “Configuring VPN Failed” state

Network management
1

We are currently conducting an internal test for an OV Terra proposal.

We are testing with two AP1321 units running AWOS 5.0.4.2028 on OV Terra.

One specific AP does not appear in OV and remains in the “Configuring VPN Failed” state.

Even after resetting and re-registering the AP several times, the issue remains the same.

There does not seem to be any issue with the DHCP Option 43 configuration, because the other AP is registered successfully.

SSL port filtering or URL filtering should not be an issue either, as we are performing the test in a network environment where there are no such filtering devices.

Has anyone who is currently testing Terra seen this kind of case before?

2

Hi mkyoo,

Configuring VPN failed generally seen due to Firewall ports are not open or SSL issues.

You will find the precise reason in the file openvpn.log and file can be found cd “/var/log” on the AP. I hope it helps

3

Hi Thanjavuru, Thank you for your response.

Following your advice, I checked the OpenVPN logs.

It appears that the TCP connection to the OpenVPN server is successful, but the connection fails during TLS certificate verification.

The OV Terra guide mentions a method to delete the existing SSL certificate, but the command returns “Permission denied” and cannot be executed.

Is there any other way to reset or remove the existing SSL certificate and obtain a new one?

4

Try the below and see it helps

rm -rf /.ocloud/callhome_hash.json /.ocloud/certificateFile.cert
/.ocloud/cloudCaChain.pem /.ocloud/privateKey.key /.ocloud/csr.csr
/.ocloud/publicKey.key ./privateKey.key.dec

reboot

see it helps. this will help to get fresh certificates from teh server

5

Thanks to prompt response.

The command you shared is the same command that I had already tried.

Below is the result of the command.

image
image936×173 5.95 KB

That is why I am currently checking whether there is another method.

It seems a little strange that the certificate information is not removed even after running sudo firstboot.

Is there any other method I can try?

6

Looks u need root access :-). Pls contact support , sorry

7

No, it was very helpful. At least I now have a clear direction on what I should check. :slight_smile:

Thank you very much for your help, and have a great day.