Framer error

Updated 11 October 2026

Short answer

Framer's own troubleshooting guide covers most problems with Framer sites, and they're almost all about the custom domain. Your DNS records must match the values Framer gives you. Remove extra A records and registrar parking records. Don't set any AAAA (IPv6) records, which Framer says can stop SSL certificates being issued. And if you use Cloudflare, turn off its proxy for those records.

What's the problem

Your Framer site doesn't load on your domain, shows a certificate or "not secure" warning, or Framer says the domain's DNS is invalid.

Why it happens

  • DNS records don't match Framer's values.
  • Extra records: leftover A records, registrar parking records, or domain redirects at the registrar.
  • AAAA records blocking SSL certificates.
  • A proxy (such as Cloudflare's orange cloud) in front of Framer.
  • DNS changes still updating.
  • The domain is attached to another project, including an archived one.

How to fix it

  1. Compare your DNS with the values in Framer's domain settings.
  2. Remove extra A records, parking records and registrar redirects.
  3. Delete any AAAA records for the domain.
  4. If you use Cloudflare, set Framer's records to "DNS only".
  5. Wait for DNS to update, then check Framer's domain settings again.
  6. If Framer says the domain is in use, check your other and archived projects.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; uptime checked every 5 minutes, with an email when the site goes down and when it is back; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them; your DNS: nameservers, addresses, DNSSEC, and records pointing at services that no longer exist; whether HTTPS works and http visitors are sent to it. It has no connection to your site builder, so check its status page as well.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. Framer: Troubleshooting custom domain issueshelp centerMake sure you do not set any AAAA records. These can prevent SSL certificates from being issued, which breaks HTTPS.
  2. Framer: Troubleshooting custom domain issueshelp centerRemove parking records created by your registrar
  3. Framer: Troubleshooting custom domain issueshelp centerDisable proxy features (e.g. set Cloudflare to “DNS only”)

Related

Webflow error Check Webflow's status page, then whether the latest changes were published to your custom domain, and whether the domain's DNS points to Webflow. Domain not working Check three things in order: the domain hasn't expired, its nameservers are the ones you expect, and its DNS records point at your current host. "Your connection is not private" The browser couldn't verify your site's certificate: it's expired, for the wrong domain, or not trusted. Fix or renew it on your server. DNS propagation: how long it takes A record change reaches everyone within its TTL, often minutes to hours. A nameserver change can take up to 24 hours. Here's how to check and speed it up.

Preventionlabs is independent and not affiliated with Framer. Product names are used only to describe the problem.

← All of Website builders