Troubleshooting
Domain Connection Issues
Most domain connection issues can be resolved by verifying DNS records, allowing time for propagation, and confirming domain settings are configured correctly.
Advanced
6 min read
Connecting a custom domain to your Framer website is usually a straightforward process, but domain-related issues can occasionally prevent a website from going live correctly.
Common problems include:
Incorrect DNS records
Domain verification failures
SSL certificate delays
Propagation issues
Redirect problems
Subdomain configuration errors
This guide explains the most common domain connection issues, their causes, and how to resolve them.
How Domain Connections Work
When you connect a custom domain, your domain provider and Framer must communicate through DNS records.
The process generally follows this workflow:
If any step fails, the domain may not connect properly.
Common Domain Connection Issues
Domain Not Connecting
One of the most common problems is when the domain remains unverified or does not connect successfully.
Possible causes include:
Incorrect DNS configuration
Missing records
Recent DNS changes
Typographical errors
Double-check all DNS records against the values provided by Framer.
DNS Changes Not Taking Effect
After updating DNS records, changes are not always immediate.
DNS updates must propagate across servers worldwide.
Propagation may take:
During this period, the website may appear inconsistent depending on location and network.
SSL Certificate Not Active
SSL certificates secure your website and enable HTTPS.
You may encounter messages such as:
SSL Pending
Certificate Processing
Secure Connection Not Available
This often occurs immediately after connecting a domain.
In most cases:
DNS must finish propagating
Domain verification must complete
SSL generation must finish
The issue typically resolves automatically once setup is complete.
Website Showing the Wrong Page
Sometimes a domain connects successfully but displays:
An old website
A parking page
A registrar landing page
A previous hosting provider
This usually indicates that:
DNS records are pointing elsewhere
Old DNS records still exist
Propagation is incomplete
Review your DNS settings and remove outdated records if necessary.
WWW Version Not Working
A common issue occurs when:
works but:
does not.
Or vice versa.
This usually means the domain and subdomain are not configured consistently.
Verify that both:
and
are configured correctly and redirect as expected.
Redirect Loops
A redirect loop occurs when visitors are continuously redirected between URLs.
Examples include:
HTTP to HTTPS loops
WWW to non-WWW conflicts
Multiple redirect rules
Visitors may see browser errors such as:
Review redirect settings and ensure only one canonical destination exists.
Domain Verification Failed
If domain verification fails, Framer cannot confirm ownership of the domain.
Common causes include:
Missing DNS records
Incorrect values
Recent DNS changes
Record conflicts
Verify all DNS entries carefully and allow time for propagation.
Incorrect DNS Records
Incorrect DNS records are responsible for many connection problems.
Common mistakes include:
Missing records
Extra spaces
Wrong values
Duplicate entries
Typographical errors
Even a small mistake can prevent successful verification.
Mixed DNS Providers
Sometimes domains are managed through one provider while DNS is managed through another.
Example:
If changes are made in the wrong location, they will not affect the live DNS configuration.
Always verify where your DNS is actually managed.
Subdomain Connection Issues
Subdomains require separate DNS configuration.
Examples:
Each subdomain typically requires its own DNS records and verification.
Domain Works for Some People but Not Others
This is almost always caused by DNS propagation.
Because internet providers cache DNS information differently, some visitors may see:
The new website
The old website
Connection errors
temporarily.
Waiting for propagation is usually the solution.
Troubleshooting Checklist
Before contacting support, verify:
DNS records match Framer requirements
No typos exist in DNS values
Domain verification is complete
SSL has finished provisioning
Old DNS records have been removed
DNS propagation has had sufficient time
WWW and non-WWW domains are configured correctly
Most domain issues can be resolved through this checklist.
How to Check DNS Records
Review the DNS settings at your domain provider.
Verify:
A records
CNAME records
Redirect settings
Nameservers
Compare each value carefully with the instructions provided during domain setup.
When to Wait
Many domain issues are temporary.
After making DNS changes, allow time for:
Propagation
Verification
SSL generation
Making repeated changes during propagation can sometimes delay troubleshooting.
Common Beginner Mistakes
Publishing Before Domain Setup Is Complete
The website may be published correctly while the domain remains disconnected.
Always verify domain status after publishing.
Editing the Wrong DNS Zone
Some users have multiple DNS providers and accidentally update records in the wrong location.
Confirm where DNS is managed before making changes.
Forgetting WWW Configuration
Configuring only one version of the domain can lead to accessibility issues.
Always test:
Domain
WWW domain
after setup.
Removing Required DNS Records
Deleting required DNS records may break:
Verification
SSL
Website routing
Only remove records when you understand their purpose.
Best Practices
Follow DNS instructions exactly
Double-check all record values
Allow time for propagation
Test both WWW and non-WWW versions
Avoid making repeated DNS changes unnecessarily
Verify SSL activation after connection
Keep DNS records organized
Review live domain behavior after publishing
Final Thoughts
Most domain connection issues are caused by DNS configuration errors, propagation delays, or incomplete verification steps.
Fortunately, these problems are usually straightforward to resolve once the root cause is identified. By carefully reviewing DNS records, allowing time for propagation, and testing both domain versions, you can successfully connect your custom domain and launch your website with confidence.
Frequently Asked Questions
How long does domain connection take?
Most connections work within a few hours, although DNS propagation can occasionally take up to 48 hours.
Why is my SSL certificate still pending?
SSL certificates often require successful domain verification and DNS propagation before activation.
Why does my domain show an old website?
DNS records may still point to a previous hosting provider, or propagation may not be complete.
Why does the WWW version not work?
The WWW subdomain may require additional DNS configuration or redirect settings.
Should I keep changing DNS records if the domain isn’t working?
No. Frequent changes can make troubleshooting more difficult. Verify the configuration and allow time for propagation before making additional changes.
Related Articles
Connecting a Custom Domain
SSL and Security
How to Publish Your Site
Updating Your Live Site
Sitemap and Indexing
Sharing Your Site
Frequently Asked Questions
What is Domain Connection Issues?
This article explains the key concepts, best practices, and practical applications related to domain connection issues.
Why is domain connection issues important?
Understanding domain connection issues can help improve implementation, decision-making, and overall results.
What are the main takeaways from domain connection issues?
The article highlights common best practices, recommendations, and important considerations readers should understand.
framerbaseio