Created cert but server still get "connection is not private" message

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
certbot certonly -a manual -d --preferred-challenges dns --staging

It produced this output:

  • Congratulations! Your certificate and chain have been saved at:
    Your key file has been saved at:
    Your cert will expire on 2019-09-06. To obtain a new or tweaked
    version of this certificate in the future, simply run certbot
    again. To non-interactively renew all of your certificates, run
    “certbot renew”
  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

My web server is (include version):
znc irc bouncer

The operating system my web server runs on is (include version):
Ubuntu 16.04.6 LTS

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
certbot 0.31.0

I created a pem file from the privkey and fullchain pem files using the below command

cat /etc/letsencrypt/live/{privkey,fullchain}.pem > znc.pem

I moved this into the .znc folder and replaced the previous znc.pem file. What did I miss?

Hi @odin

your command:

You have used the --staging - system, that’s the test system. So your certificate isn’t valid.

Remove that option and create a productive certificate.

PS: Checked your domain that’s not the current problem ( ):

The domain uses the
expires in 75 days - 1 entry

certificate, so the domain name is wrong.

Do you have an own vHost with

Or is this not relevant, because you don’t use the certificate with a webserver?

1 Like

IRC daemons don’t work with vhosts as far as I know.

1 Like

I have two subdomains on different ports, wordsmiths is the other one. I was able to generate the needed cert after I removed staging from the command (stupid mistake). All is now working.

Thanks everyone!

1 Like

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