The certificate is not trusted because it is self-signed.

Discussion in 'ISPConfig 3 Priority Support' started by Wilt, Jan 7, 2020.

  1. Wilt

    Wilt Member HowtoForge Supporter

    I am working on a new server with a clean install of Ubuntu 18.04 LTS and I have followed the tutorial:
    The Perfect Server - Ubuntu 18.04 (Bionic Beaver) with Apache, PHP, MySQL, PureFTPD, BIND, Postfix, Dovecot and ISPConfig 3.1

    I selected the option to "... secure (SSL) connection to the ISPConfig web interface" and the certificates were successfully generated. I can access ISPConfig successfully but I get the SSL error message that "The certificate is not trusted because it is self-signed". Why is this? I can view the certificate from the browser and it looks fine. Any suggestions please?
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The reason is that the SSL cert is a so-called self-signed SSL certificate which means that you are the issuer of that certificate and as your browser does not know you, it shows a warning that it does not trust the certificate. You can replace it with a certificate from let's encrypt to get rid of the browser warning.
  3. Wilt

    Wilt Member HowtoForge Supporter

    Thanks Till, now sorted :)

Share This Page