Having Challenges with letsencrypt Server side

Transferred site to siteground via Cloudflare using A record DNS and IP address. Checked dnswatch.info to make sure ip address resolved. Tried to add letsencrypt cert on hosting but certificate not being added.

Getting Your connection is not private error.
Please help.

1 Like

What’s the domain?

salesvibrations.com

its still showing the error message the site is unsecure. Not sure what you mean by whitelisting the domain. I added the siteground a record ip address for hosting but the ssl from siteground is not being applied to domain. Hope this clarifies my challenge.

Your website is using Siteground’s own certificate. Contact Siteground Support to get help with a valid certificate for your website.

1 Like

Ok thanks. Ive been with their support team and for some reason i cant get a certificate issued for the site. Will continue following up. Thank you very much for your time.

1 Like

I was with Siteground for a year and never could get Letsencrypt to work. This was in spite of help from their usually superb support team. As a work-around, I used a self-signed cert and CF Full rather than Full Strict - worked fine for my use case. Siteground rocked in all other respects, just a bit pricey for me after the initial teaser year.

2 Likes

Thank you Kenny for your response. Will definitely use this. What’s the hosting you’re using now?

MDDHosting

1 Like

Hi @user5674,

I use Siteground, and every time I need to add/renew a LE cert, I pause Cloudflare for a couple minutes. It seems that LE needs to go straight to your origin server to authenticate the cert.

However, pausing Cloudflare exposes momentarily your origin server IP address. You may want to have a look at the tips below to avoid pausing, see if they would work in this case:

2 Likes

I just tried this and it didn’t work. The error I got through the Runcloud process looks like a DNS mismatch because the Cloudflare IP address isn’t the same as the server’s IP address. It’s supposed to do a file check, but it looks like a DNS check is part of the process in this case.

1 Like

Reviewing now the Siteground documentation on how to install Let’s Encrypt, it does require that (1) IP address is the origin IP address and (2) in the case of wildcard SSL, that the server has DNS authority over the zone.

2 Likes

Hi Everyone,
Finally got it resolved. Thank you everyone for the wonderful feedback. I am grateful. Here is what i learned. I was using a separate Cloudflare account from the one provided by siteground. I used domain mapping by using the IP address provided by siteground. When adding Lets Encrpt SSL the name on the cert was different from the name of the domain hence the error message when accessing the site from a browser. This site helps with verification (https://www.sslshopper.com/ssl-checker.html) The other thing is that there is a 5 trial limit for adding LE and propagation thereafter there is a mandatory lockout before you can re-add it again.(24-72 hours) Hopefully this will help someone going through a similar scenario. Siteground support was also extremely helpful. Cheers:)

1 Like

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