| Symptom | Your next action |
|---|---|
403 with error code: 1010 and no JSON body | Cloudflare blocked the request before it reached Base44, usually because of the HTTP client’s default User-Agent. Send a normal User-Agent header from your server code. Don’t change the token. |
| Token rejected | Check the token type, the header it’s sent in, the workspace it was created in, and its permission against authentication. |
| Secret is empty in server code | Check that the secret is named exactly BASE44_WL_TOKEN and the code reads that name. On the App builder path, publish the app and check again: saved secrets don’t reach the editor preview or the background tester until a publish. |
| Plan-related rejection | Check which workspace the request used, then whether the feature is outside the plan. See tenancy and credentials and the overview. If it’s the plan, skip the feature and tell the person. |
| The agent still says Base44 | Read the settings back with GET and check that enabled is true and brand_name is saved, then try a new build. See brand. |
| Apps don’t use the design system | Check that the workspace has a default design system with status ready, and that use_default_design_system is true. See brand. |
| Insufficient credits | Ask the person to check the credit balance and add credits. Then resume the existing app rather than creating a new one. |
| Build appears stuck | Check the app’s state, then look for a question waiting on an answer. See the build turn. |
Live updates refused with whitelabel_sockets_disabled | Live updates aren’t on for the workspace yet. Tell the person to contact Base44 to turn them on. Until then, poll for the build’s state. See live updates. |
| Request times out | Check whether the app or message already exists before you send it again, and compare your timeouts with the build turn. On the App builder path, split the work into a start call and later status checks. |
| Preview fails | Check that the app is ready, that you used a fresh preview or embed token, and that the embedding policy allows your site. See embed the app. |
A chat message starting with / doesn’t send | In the Base44 editor chat, a message that starts with / opens the command menu. Ask the person to start the message with another character. |
| Works only in your browser | Open the platform in a private window as a new visitor. Find the step that depends on your own session, cookie, or local file, and fix it. |
| Anything else | Check the FAQs. |
Troubleshooting
Symptoms and next actions for the Base44 white label setup skill.
Listen to this pageabout 1 min
Find the symptom here before you retry anything. Retrying a build call can create a duplicate app or charge credits twice. When the cause is something the person can’t fix, say clearly that they don’t need to do anything.
Was this page helpful?