www.anthonygarmont.com
  • Home
  • Photo Blog
  • Portfolio
  • Tech Blog
  • Contact

SSL Certificate Gotcha with PRTG

11/8/2018

0 Comments

 
When using an internal Microsoft Certificate Authority, there was a small gotcha installing an SSL certificate on the  PRTG web interface.

Use this article in order to install the SSL certificate on the PRTG server. You will also need OpenSSL installed on a machine as well:
kb.paessler.com/en/topic/283-how-can-i-use-a-trusted-ssl-certificate-with-the-prtg-web-interface#reply-713

There is only ONE thing to note on this procedure. The COMMON NAME you give the certificate during the OpenSSL process is apparently not used at all with PRTG. So you will want to add ALL the Subject Alternative Names in the additional attributes portion of the request in IIS on CertSrv including the primary name you might use to access the server's web interface.

For example, on a server named PRTG1 you would included all these SANs:

​san:ipaddress=10.10.10.15&dns=prtg1&dns=prtg1.internaldomain.com

Which Translates to the following in the SAN portion of the cert:

IP Address=10.10.10.15
DNS Name=prtg1
DNS Name=prtg1.internaldomain.com

This allows us to hit PRTG from any of those names without a certificate warning.
0 Comments



Leave a Reply.

    View my profile on LinkedIn

    Archives

    November 2020
    August 2019
    November 2018
    June 2015
    March 2015
    December 2014
    June 2013
    July 2012
    May 2012

    Categories

    All
    Active Directory
    ADCS
    Cloud Computing
    Microsoft Excel
    Microsoft Exchange
    Microsoft Hyper V
    Microsoft Hyper-V
    Microsoft VDI
    PKI
    Powershell
    Technical

    RSS Feed

    What I believe...
Powered by Create your own unique website with customizable templates.
  • Home
  • Photo Blog
  • Portfolio
  • Tech Blog
  • Contact