If you have built and published a website using the Bouncy Website Editor but it is not loading when you visit the URL, follow this troubleshooting guide.

Symptom: You just connected a custom domain and the site shows a browser error (e.g., "This site can't be reached").

Solution: DNS changes can take up to 48 hours to fully propagate, although most changes take effect within a few hours. Wait and try again later. You can check propagation status using tools like dnschecker.org.

Symptom: The site loads on the Bouncy subdomain but not on your custom domain.

Solution: Go to the Custom Domains section in your dashboard and check the verification status. If the domain is not verified, follow the instructions to add the required DNS records (typically a CNAME or A record).

Symptom: The domain resolves but shows the wrong content or an error page.

Solution: Verify that your DNS records are pointing to the correct Bouncy hosting target. Check your domain registrar's DNS settings and compare them with the values shown in your Bouncy Custom Domains settings.

Symptom: You see a "Not Secure" warning or SSL certificate error.

Solution: SSL certificates for custom domains are provisioned automatically but may take a few minutes to activate after the domain is first connected. Wait 10-15 minutes and try again. If the issue persists after several hours, contact support.

Symptom: You see a blank page or the default Bouncy page instead of your website content.

Solution: Make sure you clicked the Publish button in the Website Editor after making your changes. Saving a draft is not the same as publishing.

Symptom: You see an old version of your website or changes you made are not appearing.

Solution: Hard-refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) or open the URL in a private/incognito window.

If none of the above solutions help, contact Bouncy support with:

See How to Contact Bouncy Support.