BillingCDN resources overviewOrigin groupPurgePrefetchReports
Chosen image
Home/CDN/Troubleshooting/Attaching or issuing an SSL certificate

An SSL certificate isn't working: how to solve to issue

Can't attach a personal certificate to a resource

Check whether there is an empty line at the end of a certificate chain. The line is often forgotten, the error occurs because of this. This is how the chain with an empty line at the end looks:

Can't attach a personal certificate to a resource

Full instructions for attaching a certificate: Add an SSL certificate to deliver content over HTTPS.

Can't get Let's Encrypt certificate

Check whether the rules you created overlap the path "/.well-known/acme-challenge/". This is the path for issuing a certificate, in many cases, such a rule (for example, with the path "/.*") does not allow issuing the certificate. Disable the rule, get the certificate, and enable the rule again.

You can check whether the rule blocks the certificate issuance path using this service.

Check whether you have added a CNAME record with our domain. Your domain's DNS records must have a CNAME record with your personal zone as the value. The certificate cannot be issued without it. You will find the value for the record in the second step of the setup guide for the resource:

Can't get Let's Encrypt certificate

If these tips don’t help, write to technical support via the chat in the corner of the screen — we will help you.

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page