Skip to main content
Find where to fix a problem with Base44, or look up what an error code means.
Quick troubleshooting tips:
  • If something in your app isn’t working as expected and you don’t see a clear error, type ‘Something is wrong’ in the AI chat. Base44 analyzes what’s happening in your app, surfaces possible issues, and suggests fixes directly in context, so you can often solve the problem before trying anything else.
  • Check the Base44 status page to see if there are system-wide problems.

​
Finding a fix

Most fixes live on the page for the feature you’re using. Choose your area to go straight to its troubleshooting.

AI chat

The chat is stuck, gets your change wrong, or won’t undo or revert.

Loading and publishing

The app editor won’t load, your app shows a blank screen, or changes don’t go live.

Backend functions

A function returns errors, won’t deploy, or can’t be reached.

App access

Your app link opens for you but not for other people.

​
Fixing a domain

Domain fixes depend on where you got your domain. If you’re not sure, see checking where your domain is registered.

Bought in Base44

A GoDaddy or IONOS domain you bought in Base44.

Bought through Wix

A domain you bought through Wix.

Another provider

A domain you connected from another provider.

​
Error codes

If you see an error code, find it below to learn what it means and what to do.
A 400 error means the Base44 server could not process your request, often because some information is missing or in the wrong format.Examples:
  • Submitting a form with missing required fields.
  • Calling an API with the wrong data format.
What should you do? Check the information you entered and try again. If using an API, make sure your request matches the expected format.
You are not logged in, or your login session has expired. The requested action requires authentication.Examples:
  • Trying to view a dashboard page without signing in.
  • Calling an API or integration feature with invalid credentials or an expired token.
What should you do? Sign in to Base44 and try again. If using integrations, update your API keys or login credentials.
You are signed in but do not have permission to perform this action or access the resource. This can happen if your role or permissions are limited, or if the data permissions for certain data tables are not properly set.Examples:
  • Trying to change settings in an app you do not have access to.
  • Attempting to access data or pages restricted by your role or your app’s data permissions.
What should you do? Check with your workspace admin to see if your permissions need to be updated. If you are an admin or developer, review the data permissions for any relevant data tables and make sure the correct access is set up for the actions you want to take.
The page, link, or resource you tried to access does not exist.Examples:
  • Entering an incorrect URL for your app or dashboard.
  • Accessing a deleted or moved file.
What should you do? Check for typos and confirm you have the correct link. If the resource should exist, check with your workspace admin or collaborators to make sure it has not been moved or deleted. If you still can’t access it, contact Customer Care.
You tried to perform an action too many times in a short time period. This triggers a temporary rate limit that protects performance and stability.Examples:
  • Rapidly clicking to reconnect a domain or repeat the same action in your dashboard.
  • Sending many repeated requests in a short time via the API, backend functions, or workflows.
What should you do? Wait a short time before trying again. When you retry, avoid repeating the same action quickly so you do not hit the limit again.Additional info:
  • Calls your app makes for a signed-in person count against that person’s own allowance, so this capacity grows as more people use your app. Visitors who aren’t signed in are counted by their IP address.
  • Calls your backend functions make with admin access, known as the service role, act for the app instead of a person. All of these calls share one allowance for the whole app, which doesn’t grow with the number of people using it. In an app that serves many teams or customers, these calls are often the first to hit the limit.
  • Paid plans get higher limits. See rate limits by plan.
  • Spread requests out over time instead of sending them all at once.
  • Use batch requests where your integration supports them.
  • Add caching so you do not call the same endpoint for the same data again and again.
  • Add retry logic that waits a short time before sending a new request after a 429 response.
  • If 429 errors appear during normal activity, contact Customer Care with the time of the error and what you were trying to do.
Something went wrong on the Base44 server while it processed your request. You might see it while loading your app, saving data, opening pages, or using features like forms. It can cause blank screens, missing data, or features that stop working, in both your preview and your live app.Examples:
  • Seeing a “500 Internal Server Error” page.
  • Features failing when saving or loading data.
What should you do? A 500 error comes from the server, so you usually can’t fix it yourself. Refresh and try again, since many 500 errors are temporary. Check the Base44 status page or the Base44 Discord for known issues.If the error keeps happening, contact Customer Care and include:
  • Your app name
  • Where and when the error happens
  • Any error messages from the browser console, with screenshots if you can
  • The steps that led to the problem
A 500 error usually means the URL for your webhook POST request is incorrect. Make sure you are using your app’s default Base44 app link as the base URL in your function endpoint.For example: https://app--your-app-name.base44.app/api/apps/your-app-id/functions/yourFunctionNameIf you have a custom domain connected, it is still recommended to use the default app link for POST requests to ensure proper routing and fewer errors. Double-check the structure of your URL and update your integration as needed.