Base44 not working: a calm triage order
“Base44 not working” almost always means one stuck moment: publish failed, live did not change, blank screen after an edit, domain pending, or data missing. Treat it as a triage, not a rewrite.
Open status.base44.com first. If Hosting or Builder is degraded, wait. Burning generation credits on a platform incident wastes money and time.
Concrete order
- Status — confirm Builder / Hosting are healthy.
- Publish — did the job fail, or succeed with stale live output?
- Blank screen — last edit, console error, preview vs published.
- Domain — host URL works, custom domain does not → DNS/SSL.
- Schema / data — entities, permissions, empty queries last.
Official troubleshooting lives inBase44 docs. Our studio page /base44-not-working is the short version of this order.
Past status and still stuck? Start a diagnostic with the error text and app URL. We isolate one fault line — we do not invent incident queues.
Questions & answers
Should I rebuild the app when Base44 feels broken?
Almost never as step one. Rebuilding burns credits and hides the real fault. Check status, then isolate publish vs blank screen vs domain vs schema.
What if status.base44.com shows everything green?
Green status rules out a platform-wide outage, not your app. Move to publish logs, the live URL vs preview, DNS/SSL, then entity data.
Blank screen after an AI edit — where do I look?
Note the last prompt or change, open the browser console, and see whether preview and published URLs match. Rollback or undo the last edit before rewriting screens.
When is it a custom domain problem instead?
If the Base44 host URL works and your domain does not (SSL pending, connection refused, wrong site), stop editing the app and fix DNS first. See custom domain SSL.
What should I send in a diagnostic?
App URL, whether preview works, exact error text, last change, and screenshots of DNS or publish logs if you have them. Use /start.