diff --git a/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx b/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx
index c402ace0ec42d37..94322164cae6868 100644
--- a/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx
+++ b/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx
@@ -111,6 +111,6 @@ Server: cloudflare
 CF-RAY: 3e1e77d5c42b8c52-SFO-DOG
 ```
 
-If SSL was not working for your domain (e.g. your SSL certificate has not yet been issued), you would see a [525](https://support.cloudflare.com/hc/articles/115003011431#525error) or [526](https://support.cloudflare.com/hc/articles/115003011431#526error) HTTP response after the redirect.
+If SSL was not working for your domain (for example, your SSL certificate has not yet been issued), you would see a [525](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-525-ssl-handshake-failed) or [526](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-526-invalid-ssl-certificate) HTTP response after the redirect.
 
 Please note that the issuing of a Universal SSL certificate typically takes up to 24 hours. Our paid SSL certificates issue within 10-15 minutes.