Connection is not private


#1

Hi there,

I’ve recently moved my website from fasthosts hosting to home server.
I’ve tested everything on a different domain, where everything worked fine.
I don’t know what could be the reason for getting the following message in browsers: This connection is not private.
Could it be because I had a different SSL cert from fasthosts, or any other reason ?
I’ve tried to renew a few times, so now I’ve reached the limit as well.

See details below

Host operating system ubuntu 18.04
web server apache latest in alpine docker container
website www.clean-property.co.uk

After checking is the cert was created I got the followings

/etc/letsencrypt
/etc/letsencrypt/keys
/etc/letsencrypt/keys/0000_key-certbot.pem
/etc/letsencrypt/keys/0001_key-certbot.pem
/etc/letsencrypt/live
/etc/letsencrypt/live/clean-property.co.uk
/etc/letsencrypt/live/clean-property.co.uk/privkey.pem
/etc/letsencrypt/live/clean-property.co.uk/README
/etc/letsencrypt/live/clean-property.co.uk/chain.pem
/etc/letsencrypt/live/clean-property.co.uk/cert.pem
/etc/letsencrypt/live/clean-property.co.uk/fullchain.pem
/etc/letsencrypt/renewal-hooks
/etc/letsencrypt/renewal-hooks/post
/etc/letsencrypt/renewal-hooks/pre
/etc/letsencrypt/renewal-hooks/deploy
/etc/letsencrypt/archive
/etc/letsencrypt/archive/clean-property.co.uk
/etc/letsencrypt/archive/clean-property.co.uk/cert1.pem
/etc/letsencrypt/archive/clean-property.co.uk/privkey1.pem
/etc/letsencrypt/archive/clean-property.co.uk/chain1.pem
/etc/letsencrypt/archive/clean-property.co.uk/fullchain1.pem
/etc/letsencrypt/csr
/etc/letsencrypt/csr/0001_csr-certbot.pem
/etc/letsencrypt/csr/0000_csr-certbot.pem
/etc/letsencrypt/accounts
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/7b81d3ff1f18765bd4a32ac6f95ce8f7
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/7b81d3ff1f18765bd4a32ac6f95ce8f7/meta.json
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/7b81d3ff1f18765bd4a32ac6f95ce8f7/regr.json
/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/7b81d3ff1f18765bd4a32ac6f95ce8f7/private_key.json
/etc/letsencrypt/renewal
/etc/letsencrypt/renewal/clean-property.co.uk.conf

Thank you


#2

Hi @boxyvision,

The browser error that I see shows the reason for this problem:

The certificate is only valid for clean-property.co.uk.

For certificate purposes, www.clean-property.co.uk and clean-property.co.uk are separate names and both should be listed explicitly in your certificate.

On your new server, https://clean-property.co.uk/ generates an immediate redirection to https://www.clean-property.co.uk/, which then produces the above error.


#3

Your certificate is only valid for clean-property.co.uk - you would need to create a new one that includes both www.clean-property.co.uk and clean-property.co.uk. How did you obtain this certificate in the first place? Doing the same thing over and over won’t change results, just hit rate limits. The good news is you can probably issue a new one for both names, as it won’t be identical to the ones you’ve issued so far (which is probably the rate limit you hit - five identical certificates per week.)


#4

Thank you very much for your quick support! I’ve deleted the old certificate, and created a new one. It works properly! I don’t know , how I did such basic mistake.
You guys are fast & fantastic !


#6

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