Certificate shows up as not secure - certificate issuer is 'example.com'


I managed to get certbot working on my debian webserver which is running a bitnami django stack image. It worked initially however, I restarted apache to call the document root of the django files and now the certificate is returning not secure.

When looking at the details of the certificate in safari, the issuer is ‘example.com’ and no longer LetsEncrypt.

When I go to the apache2.conf file and check the SSLCertificate settings all the files point towards the letsencrypt folders but are clearly not being called.


Thank you,

There could be other files in which ssl related configuration statements could be found.
If you have your Apache configuration below /etc/apache2, just run the following command to list them:

grep -ri SSLCertificateFile /etc/apache2

With the help of this list, you should be able to identify where the certificate for example.com gets assigned to a virtual host.

How exactly did you install certbot? If you followed the debian instructions on certbot.eff.org you might have unintentionally installed a second copy of apache in addition to the one that bitnami provides, with its own separate configuration. Might you have restarted the wrong apache?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.