SSL + DNS Issues - Going Live

Need help
1

Hey Bubble fam,

I’ve set up my domain blossoms.app and confirmed that my A records are fully propagated and correctly pointing to Bubble’s IPs. However, I’m running into the dreaded “We found bad DNS records for blossoms.app. We were not able to look up these records” issue that so many others have posted about, with a little twist:

Issue

*www.blossoms.app works fine and is secured with SSL.
*blossoms.app (without www) does not work and shows an SSL error in all browsers:

  • Firefox: “Did Not Connect: Potential Security Issue (HSTS)”
  • Chrome: “Your connection is not private – net::ERR_CERT_COMMON_NAME_INVALID”
  • Safari: “Can’t establish a secure connection to the server.”
  • In Bubble → Settings → Domain & Email, I removed and re-added blossoms.app, but Bubble still won’t issue SSL for the root domain and says my A records aren’t configured.
  • Because of this, Bubble won’t let me enable TLS encryption (HTTPS) for blossoms.app, stating:
    “You haven’t configured your A records yet, so you can’t set up TLS yet. It will be available once the A records are validated.”

Domain provider: GoDaddy

** What I’ve Already Tried**

Verified DNS Settings (Confirmed via WhatsMyDNS)

  • A records for @ (root domain) → Correctly set to Bubble’s required IPs.
  • A records for www → Also correct and matches Bubble’s IPs.
  • No CNAME conflicts, Cloudflare proxying, or domain forwarding enabled in GoDaddy.

Cleared Cache & DNS Locally

  • Hard refreshed site (Cmd + Shift + R on Mac).
  • Cleared browser cache & cookies.
  • Flushed local DNS cache:
    • Mac: sudo killall -HUP mDNSResponder
  • Tested on multiple devices and networks to rule out local caching issues.

Tried Forcing Bubble to Recognize the Domain

  • Deleted and re-added blossoms.app in Bubble settings.
  • Waited for full propagation (over 24 hours).
  • Bubble still won’t validate SSL for the root domain.

Would appreciate any insights or help on this!

2

Who’s your domain provider? GoDaddy?

3

And here I thought I covered all my bases :sob: Yes, it’s godaddy!

4

Yeah… I commonly see this issue with people who use GoDaddy… I don’t have a great solution except reporting it to Bubble Support or using another DNS provider like Cloudflare. Never had any issues when using Cloudflare

1 Like
5

And just like that! Hours of trouble shooting and waiting around fixed by a simple switch to Cloudflare, thanks for the support Johnny - I appreciate you!

For anyone else running into this issue, fix took 5 minutes to setup and site is up and running in under 30 minutes!

6

Awesome! :raised_hands: Glad that worked for you!

1 Like
7

This topic was automatically closed after 70 days. New replies are no longer allowed.