QAlaunch

Base44 custom domain not working: causes and fixes

A Base44 custom domain that stays on Pending verification or shows errors almost always has the wrong records, leftover records, or a proxy in the way. Base44's docs ask for an ANAME or ALIAS at the root to base44.onrender.com (or an A record when ALIAS is not offered) and a CNAME on www to the same target; check the current values under DNS instructions. Remove AAAA records, parking and forwarding, set Cloudflare to DNS only, then click Verify.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

The Domains page in Base44 says Pending verification for hours. Visitors see a 502 Bad Gateway, a certificate warning, the registrar's parking page or your old site. New pages sometimes return 404 on the custom domain while the Base44 address works.

Why it happens

1. Records that point somewhere else

Base44's docs (as of October 2026) list ANAME or ALIAS at @ pointing to base44.onrender.com, or A at @ to 216.24.57.1 if your provider lacks ALIAS, and CNAME at www to base44.onrender.com. Typing the full domain in the host field instead of @ or www is a common slip.

2. Hidden leftovers

Old A records, AAAA records, or registrar forwarding and parking features add their own records. Base44 notes these can block verification or send visitors to the old site.

3. A proxy in front of Base44

With Cloudflare's orange cloud on, Base44 cannot confirm the domain. Its docs warn proxied records can make new pages 404 and stop crawler copies refreshing.

4. Registrar-side blocks

A CAA record that excludes Base44's certificate authorities, a DNSSEC record left over from an old DNS host, or a domain on clientHold at the registrar all keep the domain from going live.

How to fix it

  1. In the app editor, open Dashboard > Domains, click More actions next to the domain and choose DNS instructions. Copy the values from the ANAME/ALIAS or A record tab.
  2. Make the change where your nameservers point (Cloudflare if they point there, not the registrar). Enter only @ or www in the host field.
  3. Delete any other A record on the root, every AAAA record, and any www CNAME that points elsewhere. Switch off URL forwarding and parking at the registrar.
  4. In Cloudflare or any proxying DNS host, set the Base44 records to DNS only.
  5. If SSL still fails, review CAA records, and if you moved DNS hosts recently, update or remove the DNSSEC DS record at the registrar. Run a WHOIS lookup to rule out clientHold.
  6. Click the refresh icon next to the domain or More actions > Verify. DNS can take up to 48 hours; track it on whatsmydns.net rather than editing again.

Prompt to paste into Base44

No prompt is needed: this is fixed at your DNS provider, not in the app. Base44 can also add the records for you through Set up DNS for me if your provider supports it.

How to check it's fixed

  • Open https://yourdomain.com and https://www.yourdomain.com in a private window; both should load the app with no warning.
  • Check the Domains page shows Verified, then publish a small change and confirm it appears on the custom domain.

What a QAlaunch scan shows for this

  • Server errors such as 502 when the scan loads the domain.
  • A failed HTTPS load or certificate problem on the address you scan.
  • Screenshots that show a parking page or the old site instead of your app; the scan cannot inspect the DNS records behind it.

See exactly what a full report contains in the sample report.

Frequently asked questions

Which Base44 plan do I need for a custom domain?

Base44's docs say custom domains are available on Starter and higher. Connecting a domain you already own adds no Base44 charge beyond the plan.

Why does my domain show 502 Bad Gateway?

Typically the records point at Base44 but something in between, often a proxy or a stale record, breaks the connection. Set records to DNS only, remove extras and verify again; if it persists after propagation, contact Base44 support with screenshots.

Does connecting the root also connect www?

Yes, Base44 connects the www version along with the root, as long as the www CNAME exists. Wildcard subdomains are not supported, so add each subdomain separately.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Base44-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Base44: all Base44 fixes · Base44 testing · the Base44 pre-launch checklist

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Base44 docs: connecting an external domain · Base44 feedback: custom domain shows bad gateway