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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Hello, the owner of the website does not know how the certificate was obtained or when. I have been helping him with his website for the past couple of years and this is a new problem we haven't encountered before.
I can determine that Let's Encrypt renewed the certificate back in June of this year but it has now expired. We need to get it renewed to get his website back up and operational. I don't have enough of a technical background to easily figure this out. Any help would be appreciated. I am hoping Let's Encrypt can tell me who the renewals email are sent to.
If I were inclined to guess, I'd say your hosting service provider messed up. Do you see anything at all related to certificates in their control panels?
This domain is hosted by Bell Hosting here is Canada. In talking with their technical support, they tell me I should be able to contact Let's Encrypt and simply ask to have the security certificate renewed.
Is there an easy means of making this happen?
Thank you very much for your help. I'm out of my depth on this subject.
Your DNS is hosted there but your website is a WIX based site
Bell Canada's tech support is completely wrong that Let's Encrypt can renew certs for you. An ACME Client program must request a cert from the Let's Encrypt Server. In this case I am very confident that request is handled on wix. In any case, it is not something LE can do without being asked by an ACME client by the website operator.
Do you know how wix got involved? Do you have an account there or was there some other reseller involved.
Why do I say wix is the proper contact? Because:
This request shows your website responses
curl -Ik https://www.ernestjohnsonantiques.com
Note the various response headers naming "wix"
But most indicative is "Server: Pepyaka" is the proprietary WIX server
HTTP/2 200
date: Mon, 18 Sep 2023 20:36:05 GMT
link: <https://static.parastorage.com/>; ... <https://static.wixstatic.com/>;
x-wix-request-id: 1695069365.716771614727812418
server: Pepyaka/1.19.10
It appears that Bell Hosting uses meganameservers.com as a nameserver provider (as do many other registrars/hosts). Bizarrely, this service's homepage doesn't seem to functionally support TLS/SSL.
So @daneharris just to clarify, the domain DNS is hosted with bellhosting.ca via meganameservers but that's besides the point really.
The site is 100% hosted on WIX, if the client is not currently paying for wix that would suggest the reason their cert wasn't renewed was because they didn't pay wix hosting. It's confusing, but it's not a debate - that's just what the site is and how it works.
Thank you Mike. I have successfully corrected the problem with help from Wix Technical Support. I really appreciate the many helpful responses from the Let's Encrypt community.
