Submit a ticketCall us

AnnouncementsCome see SolarWinds at VMUG Frankfurt

SolarWinds is delighted to attend the upcoming VMUG which will take place at Kap Europa in Frankfurt on June 19th, 2018.

See event details.

Home > Success Center > Web Help Desk (WHD) > Self-signed certificate not being accepted

Self-signed certificate not being accepted

Updated March 14, 2017


The web browser is displaying errors when opening the WHD Web Console through HTTPS with self-generated certificate.



WHD 12.x


WHD is working as expected. The certificate warnings shown by web browser are correct: a self-signed certificate does not have Root CA. The connection is encrypted, it's just web browser telling you that it can't establish where the certificate came from. So basically for self-signed certificates web browser will always warn you.

To avoid warnings, the certificate must have proper certification path. So you either use public CA and buy a certificate or use local CA (for example installed on Active Directory server) to generate a certificate.


In the first case, no additional steps are needed: just install CA reply and everything will work. In a case where you are using internal CA, you still have to install Root CA certificate on all workstations. This will tell web browsers (except Firefox) where the Root CA for webhelpdesk.local is. Firefox is using built-in certificate store which is independent of the OS.

Installing Root CA can be either manual (import certificate into Trusted Root Certification Authorities), or by using group policy.

If you don't want to go with Windows CA route, you can use OpenSSL to create your own CA. In that case, you still have to distribute Root CA cert to all clients/web browsers. Here are more details on it:


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified