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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
squarespace
I can login to a root shell on my machine (yes or no, or I don’t know):
no
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
squarespace
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
I have seen from some of the other posts in this forum that squarespace has issues issuing (heh) certificates from time to time. I was just hoping that you could tell me if there is currently a technical issue issuing this cert, or if it’s truly dns cache time.
This would be a matter directly related to squarespace, as they are responsible for requesting / installing / renewing your certificate.
Currently, there aren't any issue related to Let's Encrypt Service, and only squarespace would know if they have any issue with their automation.
Hi @wulfmann, sorry to hear you're having troubles.
I'm only aware of one specific problem related to mit.edu rate limiting. If you're having trouble with a different domain with Squarespace I'd second @stevenzhu's suggestion (thanks!) that you contact Squarespace support. They would need to provide more information about what the delays are. There aren't any ongoing issues on the Let's Encrypt side.