Fix Flipsnack custom domain issues with Cloudflare

Overview

Custom domain problems between Flipsnack and Cloudflare are usually caused by the CNAME record's Proxy status being enabled. You fix it in Cloudflare's DNS settings by adding or editing the CNAME record pointing to the value Flipsnack gives you, then disabling Proxy status on that record. This lets traffic reach Flipsnack's servers directly instead of routing through Cloudflare's proxy.

How to turn the proxy off

Step 1: Sign in to Cloudflare and pick the domain

Log in at cloudflare.com.
From the dashboard, choose the domain you are using for Flipsnack.

Step 2: Open DNS settings

Click the DNS tab.

Step 3: Add or find the CNAME record

If the record does not exist yet:

Click Add record and choose CNAME as the type.
In Name, enter the subdomain you want, for example portfolio if the full domain is portfolio.yourdomain.com.
In Target, paste the value Flipsnack shows you under Branding, where you set the custom domain up.

If it already exists, find the CNAME record that points at Flipsnack.

Step 4: Switch Proxy status to DNS only

In the Proxy status column, that record shows an orange cloud.
Click the orange cloud so it turns grey. The status now reads DNS only.
Save, and check the record still reads DNS only afterwards.

DNS changes take time to spread. If the domain still fails an hour later, troubleshooting DNS setup and propagation covers what to check next.

Why the proxy has to be off: when Cloudflare's proxy is enabled (orange cloud icon), it routes traffic through Cloudflare's servers. This can cause issues with how Flipsnack verifies and handles custom domains. By switching to DNS only (gray cloud icon), you ensure that traffic goes directly to Flipsnack's servers, allowing for proper verification and functionality of your custom domain.

Next steps

Need expert support?

Our team is here to help. Connect with our team experts or message us via the live chat for personalized assistance.