SSL certificate issues
SSL is handled entirely by Cloudflare at the edge, before a request ever reaches your redirect rules. So when something's wrong with it, it shows up as a browser or connection error, not a broken redirect.
What you'll actually see
If DNS is set up but the certificate isn't ready yet, an HTTP request still gets redirected to HTTPS as expected, but that HTTPS request then hits a domain with no valid certificate, so the browser shows a hard certificate warning ("Your connection is not private" in Chrome), not a soft notice. If DNS isn't set up at all yet, the browser can't connect to the domain in the first place, that's a DNS issue, not an SSL one, see Domain Stuck on Pending.
Normal timeline vs. actually stuck
In the first 5 minutes, Cloudflare is just setting things up internally, normal. Between 5 and 15 minutes, it's actively validating and issuing the certificate, still normal if your DNS is correct. If you're at 15 to 30 minutes, open DNS Settings and click Verify DNS to confirm your records are actually resolving, this stage can occasionally reflect DNS propagation lag rather than an SSL problem. Past 30 minutes with fully verified DNS and SSL still not active, treat it as genuinely stuck and check the causes below.
If a TXT record shows up
Certificates are normally validated automatically without any extra record. If the app shows an additional TXT record to add, Cloudflare has fallen back to a different validation method, usually because the automatic method didn't succeed. Add the record at your DNS provider, and issuance typically completes within a few minutes after that. See DNS Setup Guide for how to add it.
CAA records blocking issuance
If your domain has CAA records that don't permit Cloudflare's certificate authorities, issuance will stay blocked until you add the required entries. See SSL Certificate Setup for the exact records to add.
Already using Cloudflare for this domain
This is the hardest case to spot, because everything looks fine in the app. If your domain is already on Cloudflare with proxying turned on (orange cloud), DNS can check out and your domain can show as Connected, records resolve, so that check passes. But HTTPS traffic hits your own Cloudflare zone instead of ours, which means our certificate can never finish validating. SSL stays stuck indefinitely with no obvious signal pointing to why. If your domain is on Cloudflare, set the relevant records to DNS only (grey cloud) rather than proxied.
Still stuck
Email support@redirect.supply with your domain name, we can check the certificate status directly on our end.