After updating from PRTG 9 to version 12, my custom SSL certificate is not displayed any more. The PRTG web server reverted to the default (demo) certificate and shows a certificate warning when trying to connect to the web interface.
What can I do?
Lost SSL certificate files after updating to PRTG 12. What can I do?
Modified on 2025-06-10 14:42:42 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
This article applies to PRTG Network Monitor 12
Recovering "Lost" SSL Certificates
If you have your own custom SSL certificate, purchased and installed for the PRTG web server, it might not be active after updating to PRTG 12 using the auto-update function. In the current release, this is already fixed.
This article is only relevant for you if
Steps to Go
For some installations, PRTG cannot correctly take over your custom SSL certificates (which are stored in the /cert sub folder of your PRTG program directory. Usually, your custom files still exist, but are overruled by PRTG's default certificates. You can solve this issue by going through the following simple steps.
Done. Now your original certificate files should be active again.
May, 2012 - Permalink