Skip to content

Commit 8fd31b6

Browse files
authored
fix(edge): correct error troubleshooting (#3884)
1 parent 4e2b328 commit 8fd31b6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

network/edge-services/reference-content/ssl-tls-certificate.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ If there is a problem generating your managed Let's Encrypt certificate, an erro
6565
| Error | Solution |
6666
| ------------------------------------------------------------------------|---------------------------------------------------------------------|
6767
| Too many certificates already issued for this domain | Wait, before retrying. This error occurs when you hit the limit of generating 50 Let's Encrypt certificates in a rolling 7 day period for the same domain. |
68-
| Internal managed certificate error | [Open a support ticket](https://console.scaleway.com/support/tickets/create). There has been an unspecified error in generating a managed Let's Encrypt certificate for your subdomain. |
68+
| Internal managed certificate error | There has been an unspecified error in generating a managed Let's Encrypt certificate for your subdomain. Try [resetting your domain to the default endpoint](/network/edge-services/how-to/configure-custom-domain/#how-to-reset-your-customized-domain), and then recustomizing it again, to trigger generation of a new Let's Encrypt certificate. If that fails, [open a support ticket](https://console.scaleway.com/support/tickets/create). |
6969
| Certificate cannot be renewed - Your CNAME record is no longer accurate | Your CNAME record has either been deleted or modified. Without a correct CNAME record, we cannot renew your managed Let's Encrypt certificate. [Rectify your CNAME record](/network/edge-services/reference-content/cname-record/#how-to-create-a-cname-record), and when Edge Services detects the correct record exists, your certificate will be automatically renewed. |
7070

7171
## Using your own certificate

0 commit comments

Comments
 (0)