Failed to read certificate from database after enabling/disabling IPSec VPN blade (centrally managed

[jennyado]

Hi everyone,

I’m managing a centrally managed SMB appliance that does not use the IPSec VPN blade (no site-to-site or remote access VPNs configured).

Recently, I noticed that the IPSec certificate was about to expire, so I temporarily enabled the IPSec VPN blade and clicked Renew, but I did not publish the changes.
After that, I disabled the blade again and then published the changes.

Since then, whenever I try to view the certificate in SmartConsole → IPSec VPN → Certificate, I get the message:

Failed to read certificate from database

And when I try to renew it again:

Generated keys was not found in database

The gateway is fully operational, SIC communication works fine, and there are no VPNs or blades relying on IPSec.

My main questions are:

• Could this inconsistent VPN certificate state affect anything operationally (e.g., SIC trust, policy installation, etc.)?

• Is there a recommended way to “clean up” or reinitialize the missing certificate reference without re-enabling the VPN blade?

• Has anyone seen this behavior before when enabling/disabling the VPN blade without publishing in between?

Environment details:

• SMB appliance (centrally managed)

• R81.20

Thanks in advance for any insights or similar experiences!

[the_rock · Accepted solution]

Do this...enable blade, push policy, renew cert push policy, disable blade, install policy, done.

Andy

[the_rock]

@jennyado Hope that worked?

Andy

[jennyado]

Yes, it worked. I was just afraid it would be harmful, but it wasn't. Thank you very much.

[the_rock]

Never harm for this, glad we can help. You are very welcome.