Introduction
If you’re using a custom domain with Gamma and running into issues like too many redirects or security certificate errors, it may be due to misconfigured Cloudflare settings. This guide will walk you through how to resolve these problems and ensure your gamma site is verified and accessible.
Using Cloudflare DNS with Gamma
If your domain's DNS is managed in Cloudflare, a few Cloudflare settings affect whether your custom domain connects to your gamma site.
🔷 Note: Certain SSL and security configurations in Cloudflare must be correctly set for your custom domain to work smoothly.
How to Fix DNS Issues Using Cloudflare
Recommended: Set Your Gamma Records to DNS Only (Grey Cloud)
In your Cloudflare dashboard:
• Go to DNS > Records
• Find your Gamma records (both A records on @ and the www CNAME, or your subdomain's CNAME)
• Click the orange cloud next to each record so it turns grey (DNS Only), then save
This is the recommended setup for Gamma sites. With your records set to DNS Only, you don't need the proxy settings in the next section. Verification usually takes a few minutes but can take up to 24 hours.
If You Need to Keep Cloudflare's Proxy (Orange Cloud) On
Only follow these steps if you can't switch your Gamma records to DNS Only.
Step 1: Resolve “Too Many Redirects” Error
Navigate to your Cloudflare dashboard and update your SSL/TLS setting:
• Go to SSL/TLS > Overview
• Locate Custom SSL/TLS settings
• Select Full (Strict)
This setting ensures secure communication without triggering redirect loops.
Step 2: Fix Certificate Error During Domain Verification
If your domain is still showing as “pending” and you’re encountering certificate errors:
• Go to Security > Settings
• Find the Security Level option
• Set it to Medium during the verification process
This adjustment helps smooth the handshake between Gamma and Cloudflare during site setup.
Step 3: Revert Settings Post-Verification (Optional)
Once your site is verified and running correctly, you can reset the Security Level to your preferred setting.
FAQs & Common Issues
Why is my custom domain not verifying?
Make sure your Gamma DNS records are correctly pointing to Gamma and set to DNS Only (grey cloud). If you keep Cloudflare's proxy on, set your Security Level to Medium during verification.
What does “Too many redirects” mean?
This usually means Cloudflare's proxy is on and the SSL/TLS setting is mismatched. Set your Gamma records to DNS Only (recommended), or, if you need the proxy on, switch to Full (Strict) mode in Cloudflare.
Can I change Cloudflare settings later?
Yes. Once your domain is verified, you’re free to adjust settings like Security Level as needed.
My domain shows 'Failed' in Gamma even though my DNS looks correct in Cloudflare — could DNSSEC be the issue?
Yes. If you recently transferred your domain to Cloudflare from another registrar, leftover DS (DNSSEC) records may be blocking verification. In Cloudflare, go to DNS → DNSSEC and disable DNSSEC, or remove any DS records present. After removing them, click FAILED next to the domain in Publishing & domains, or remove and re-add the domain in Gamma, to trigger a fresh verification attempt.
I'm seeing ERR_QUIC_PROTOCOL_ERROR on my custom domain after setup
This is often a QUIC/HTTP3 conflict when Cloudflare's proxy is enabled. First, ensure your Gamma DNS records (both A records and the CNAME) are set to DNS Only (grey cloud icon) rather than Proxied (orange cloud) — this is the recommended configuration for Gamma sites. If you need Cloudflare's proxy enabled, try disabling HTTP/3 under Speed → Optimization → Protocol Optimization.