Skip to main content
Sometimes things do not go as planned, but you can quickly fix most problems and get back on track. Use this guide to troubleshoot common issues with publishing, login, chat, and other key features.

​
Editor and Dashboard

You cannot access your app’s landing page because of how Base44 manages privacy settings for apps with both public and private areas.By default, Base44 requires every app to set one privacy level for all its pages. If your app’s privacy is set to “Private (Login Required),” all pages, including the landing page, will require a login. At this time, Base44 does not support making one page public (like a landing page) while the rest of the app stays private.To fix it, you need to make your app public so everyone can access your landing page.
  1. Go to your app’s dashboard.
  2. Click Overview.
  3. Under App Visibility, select Public.
If your app needs both public and private areas, follow this workaround:
  1. Create a separate app for your public landing page.
  2. Publish both apps.
  3. Link this landing app to your main, private app.
  4. Assign your primary domain to the landing page app, and a subdomain to your private app.
Tip: Try viewing in an incognito window to check access without being logged in.
For more on privacy settings, see the Authentication guide.
If you see a white screen in the editor, this usually points to a technical problem that needs further review.Here are some steps you can try:
  1. Click Revert this to restore your app to a previous working version.
  2. Open the Version History (the clock icon in AI chat) and roll back to an older version where clicking on something did not cause a white screen.
  3. Try describing your problem to AI chat with more specific details, such as exactly where, when, and how the issue appears.
If these steps do not resolve the problem, this might be a bug in your app’s code or configuration. In this case, submit a support ticket with detailed information about what triggers the white screen, which device/browser you are using, and any screenshots or error messages you see. This will help the Base44 team investigate and resolve the issue.
This error can happen if your app name contains an emoji or a special character that is not supported. When this error occurs, you will not be able to open the app editor or rename your app.If you encounter this issue, contact Base44 support so the team can help escalate your case.
When you try to open the Base44 app editor, you might see a blank screen, get stuck on the loading icon, or notice that everything is running slowly or unresponsive. This can happen for several reasons related to your browser, internet connection, or temporary platform issues.Try these steps:
  1. Check that you’re using an up-to-date, supported browser.
  2. Clear your browser cache and Base44 cookies.
  3. Turn off browser extensions, especially ad blockers or privacy tools.
  4. Open the editor in an incognito window or try a different browser.
  5. Check the Discord community for any reported outages.
  6. If the editor still isn’t working, take a screenshot of any errors (especially from your browser’s console), and contact Base44 support with your browser and operating system details.
Sometimes after publishing your app, updates such as new content, design changes, or bug fixes don’t appear on your live site. This can be caused by caching, deployment issues, or missed steps in the publishing process.Try these steps:
  1. Clear your browser and device cache, then reload your app.
  2. Double-check your app from a different browser or device.
  3. Make sure you clicked Publish and saw a “success” message.
  4. If you updated a backend function, redeploy it from the dashboard.
  5. Look for any error logs in your Base44 dashboard.
  6. If nothing works, include your app link and details about what’s missing when you contact Base44 support.

​
AI Chat

If you notice your credits are being used up faster than expected, it may be because you are chatting with the AI in regular mode instead of Discuss mode. When you work with the AI in regular mode, each interaction spends more credits. Discuss mode helps save credits by letting you plan and review steps without triggering costly AI actions.To save credits while chatting with the AI:
  1. Click Discuss in the AI chat window before you start chatting. The Discuss button should be highlighted.
  2. Plan, ask questions, and talk through your ideas with the AI.
  3. When you are finished discussing and ready for the AI to take action or build something, click Discuss again to turn it off. The Discuss button will no longer be highlighted, and then you can ask the AI to implement your changes.
2025 09 14 14 27 32 Pn
**Tip: **Always use Discuss mode for planning and brainstorming. Turn it off only when you want the AI to perform actions, generate outputs, or make changes. The Discuss mode only uses 0.3 credits per request.
For more information about how credits work and the best ways to manage them, learn more about your credits.
Sometimes the AI chat panel or Discuss mode may fail to load, get stuck loading, or give no response at all. This can be caused by browser settings, network issues, or temporary outages.Try these steps:
  1. Click Revert this on a previous prompt.
  2. Refresh your browser and check your internet connection.
  3. Clear your browser cache.
  4. Turn off any browser extensions that could block scripts.
  5. Open your app in a private or incognito window.
  6. If it’s still not working, check Discord for reported issues.

​
Data and Security

Row-level security (RLS) rules control which users can access specific data in your app. If unauthorized users can see or edit data, or RLS rules are not working as expected, use the built-in security check to find and fix issues.To troubleshoot RLS problems:
  1. Go to your app’s dashboard and click Security.
  2. Click Start security check to scan for missing or misconfigured RLS rules.
  3. Review the issues found and click Apply Fixes to use the recommended safe defaults, or adjust rules for each data entity manually.
  4. Sign in with different user roles to confirm only authorized people can access each type of data.
For more details on setting up and managing security rules, see the guide to managing security settings.

​
Performance and Speed

You may see a “500 Internal Server Error” message while loading your app, saving data, accessing pages, or using platform features like forms or dashboards. This can lead to blank screens, missing data, lost progress, or features not working.This issue is usually caused by a problem on the Base44 backend or with the platform configuration, such as an invalid App ID, server outages, deployment issues, API problems, or overloaded resources. It can affect both published and development versions of your app.A 500 error means something went wrong on the server side, and you usually cannot fix it yourself.What you should do:
  1. Refresh the page or try again later, as some 500 errors are temporary.
  2. Check the status page or Discord channels to see if there is a known platform incident.
If the problem continues, contact Base44 support. Include the following details:
  • Your app name
  • Where and when the error happens
  • Any error messages from the console (screenshots if possible)
  • What steps led to the problem
Sometimes, an app fails to load and only displays a blank screen, loading spinner, or basic header. You might see this after making edits, trying to preview your app, or after publishing. The issue can occur on both web and mobile devices and can include issues such as:
  • The app loads briefly, then disappears.
  • Clicking the app link shows nothing but a white page or loading wheel.
  • Some pages, tabs, or features remain frozen and unresponsive.
  • The app crashes when clicking buttons or making selections.
  • Nothing appears when trying to access the dashboard, preview, or key pages.
Most loading issues are caused by a problem in your app’s code or a temporary platform issue.Try the following steps:
  1. Refresh the page or open the app in a new browser window.
  2. Clear your browser cache and cookies, then try loading again.
  3. Make sure your internet connection is stable.
  4. Switch browsers or devices to see if the issue persists elsewhere.
  5. If you made recent edits before the issue started, try reverting your most recent changes if possible.
  6. Wait a few minutes. Sometimes the platform is updating or experiencing temporary downtime.
If your app still won’t load, contact Base44 support and provide:
  • A description of what you see (e.g. blank page/spinner)
  • When the issue began and any recent edits you made
  • The app name or link
  • Any error messages shown in your browser console (if possible)
The support team will investigate and work with you to restore your app.
If you’re stuck in an infinite loading state after using all your credits or after a large edit, mention this in your message.
If you see any warnings in your browser or development tools about the Tailwind CDN script (such as “cdn.tailwindcss.com should not be used in production”), there’s no need to worry. The Tailwind CDN script is added automatically by the Base44 platform and is required for your app’s styling. This script cannot be removed or disabled at this time.The warning does not affect your app’s functionality or security. The script ensures consistent styling and a stable experience across all Base44 apps.Base44 is working on a solution for this in the near future. For now, please keep the script as part of your app setup.

​
Apps and Integrations

Backend functions are designed to handle POST requests and are not accessible in a browser. If you visit a backend function URL in your browser, you will always see an error. However, if all your backend functions return 404 Not Found errors, especially when using the dashboard test tool or in your external integrations, this is a critical issue. It usually points to a problem with your app’s routing or deployment, not your code or configuration.Follow the steps below to test your backend function using the dashboard, and then proceed to the troubleshooting steps.
  1. Click Dashboard in your app editor.
  2. Click Code.
  3. Click Functions.
  4. Select the relevant function.
  5. Click Test Function at the bottom right.
  6. (Optional) Copy the function URL from the top right sidebar for use in integrations.
  • If the test passes: Your backend function is working. Errors from visiting the URL in a browser are normal.
  • If the test returns a 404 error or none of your integrations are working: Continue with the troubleshooting steps below.
  1. Confirm your plan supports backend functions: Make sure you are on a Base44 plan that includes backend function support, such as the Builder tier.
  2. Check backend functions are enabled: Go to your app settings in the Base44 dashboard and verify backend functions are enabled.
  3. Verify file locations and naming:
    • Make sure your function files (e.g. ebayAuth) are in the correct directory.
    • Check file and function names for typos.
    • Each file should export the function using Deno.serve().
  4. Redeploy your app: Redeploy from the dashboard to trigger a fresh deployment and update app routing.
  5. Review recent build and deployment: If your app was recently updated, check that all build and deployment steps completed successfully.
If the problem continues after these checks, this is likely a platform-level routing or deployment issue rather than something wrong with your app setup. Contact Base44 support and include:
  • The link to your app
  • A list of affected backend function names (for example, ebayAuth)
  • Screenshots showing the 404 errors at each endpoint
  • When the issue started, such as after a deploy, migration, or platform update
Tip: Mentioning when the issue began helps the support team troubleshoot the problem faster.
For security reasons, external services like Stripe, OpenAI, or Notion don’t let third parties (even Base44) access your credentials automatically. API keys are like passwords for services. Keeping them private and user-controlled keeps your data safe and ensures only you authorize access.Instead, you need to:
  1. Log in to the service.
  2. Go to the API or developer section.
  3. Generate your key.
  4. Paste it into Base44 as a Secret.
Once added, your app can use that key behind the scenes safely, and without code.
Backend functions in Base44 only support POST requests, not GET. This is intentional because POST lets you send data securely in the request body, while GET would expose parameters in the URL and is not meant for server-side logic.To pass data to your function, use the body of a POST request so your function receives it correctly.
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.

​
Domains

When your domain is stuck on “pending” after updating DNS to add it to Base44, this usually means there’s an issue with your DNS configuration or propagation.First, check that your nameservers are set up correctly. Read our guide on domains to check this. If you are still having issues, follow the steps below.Troubleshooting steps:
  1. Remove any AAAA (IPv6) records for your domain, as these can interfere with proper setup.
  2. Wait 48–72 hours for changes to fully propagate across the internet.
  3. Use a tool like whatsmydns.net to confirm your updated records are visible globally.
  4. Double-check that you entered the exact record values.
  5. If the status is still pending after about 30 minutes, try unlinking the domain in Base44, then re-adding it.
If your domain still does not connect, contact support with:
  • A screenshot of your DNS records
  • Your domain name
  • Your Base44 app link
If you purchased your domain in Base44, you need to verify it first. If you skip this step, your domain will not connect.You need to confirm your domain ownership by verifying your email address with IONOS.
Check your inbox for an email from support@ionos.com with the subject “Please Confirm the Contact Details for Your Domain.” Open this email and click the “Confirm Email Address” button within 14 days. This step is required by ICANN to keep your domain active and ensure your contact details are valid.If you do not confirm your email address within 14 days, your domain may be deactivated according to ICANN’s requirements. If you cannot find the email, check your spam or junk folders. If the email or link has expired, contact IONOS support to request a new confirmation email.Here’s what you need to do:
  1. Open the IONOS email and click the link to confirm your email address.
  2. In Base44, go to your app’s Dashboard and click Domains, select the domain, and click Unlink domain.
  3. Connect the domain again.
  4. Wait a few minutes for the connection to complete.
If your domain is stuck in ‘Connecting’ status for longer than 30 minutes, go to your app’s dashboard and click Domains, then unlink and link the domain again.
 Run through this checklist to set that it is set up correctly:
  • Make sure DNS records match exactly what’s shown in this guide for your setup type.
  • Remove any AAAA (IPv6) records, as they can block connections.
  • Double-check for typos. Be sure to copy and paste values exactly from this guide.
  • Ensure both www and the root domain are set up correctly.
  • Confirm your domain is renewed and active.
  • Wait up to 72 hours for changes to take effect.
    Tip: If your domain uses a DNS manager like Cloudflare, update the records there instead of at your registrar.
If you encounter SSL errors or an ERR_SSL_PROTOCOL_ERROR after connecting your custom domain to Base44, follow these steps to resolve the issue:
  • Check that your domain’s DNS records match exactly what is shown in your Base44 dashboard.
  • Remove any AAAA (IPv6) records from your DNS settings, as these can block secure connections.
  • Carefully check for typos or missing values in your DNS entries.
  • Make sure both your www and root domain point to the correct Base44 IP addresses or CNAME.
  • Verify that your domain registration is active and has been confirmed.
  • Allow up to 72 hours for DNS and SSL changes to fully propagate worldwide.
  • If you use a DNS service like Cloudflare, update your records directly within that service.
If you still see SSL errors after completing these steps, submit a support ticket and include:
  • A screenshot of your current DNS records
  • Your domain name
  • A link to your Base44 app
If you’ve deleted an app and are trying to connect the domain to a new app, you might see an error saying the domain already exists. This can happen if the domain is still registered in our system, even after the old app is removed.You won’t be able to fix this on your own right now. Please contact our support team for help on this.
After purchasing a domain from us, you need to verify your contact information to activate it. If you have not received a verification email from IONOS (the domain registrar), your domain may not connect or work as expected. This can prevent your website from going live.To resolve this issue:
  1. Check your inbox, spam, and junk folders for an email from IONOS.
  2. If you cannot find the email, contact IONOS (the domain registrar) and request a new verification email.
  3. When you contact IONOS, provide your domain name and explain that you have not received the verification email after purchasing your domain.
  4. Follow the steps from IONOS to complete your domain verification.
A 429 error usually appears due to a temporary limit on the Base44 side. This issue resolves itself automatically.

Wait a few minutes before trying to reconnect your domain. If the problem continues after waiting, try again later.
If you are still having problems with your domain, contact Base44 support and include:
  • A screenshot of your DNS records
  • Your domain name
  • A link to your Base44 app

​
Content and Media

Uploading videos to the AI chat is not supported. Instead, you can link to videos hosted elsewhere (such as YouTube, Vimeo, Loom). If you would like this feature let us know on our Feedback board.
This error appears when you try to upload a file format that is not supported by Base44 AI chat modes. You can only upload specific image types or document formats, and uploading an unsupported file triggers this message.To fix the issue:
  1. Check that your file is one of the supported formats.
  2. Make sure your file does not exceed the size limits set by Base44.
  3. If you accidentally uploaded a wrong file, click Revert this to undo the last step.
  4. Try uploading your file again using a supported format.
For more details on supported files, see the Media guide.

​
Error Codes

The action you tried completed successfully. You usually will not see this code in the Base44 interface, but you might spot it in API responses, logs, or integration tools.What should you do? No action is needed. This means everything is working correctly.
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 Row-Level Security (RLS) settings for certain data entities 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 RLS rules in your app.
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 RLS rules for any relevant data entities 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 teammates to make sure it has not been moved or deleted. If you still can’t access it, contact Base44 support.
You have tried to perform an action too many times in a short time period. This is a temporary rate limit.Examples:
  • Rapidly clicking to reconnect a domain.
  • Sending repeated requests via the API or automations.
What should you do? Wait a few minutes before trying again. Slow down repeated actions to avoid hitting the rate limit.
There was a problem with the Base44 server when processing your request.Examples:
  • Seeing a “500 Internal Server Error” page.
  • Features failing when saving or loading data.
What should you do? Refresh and try again. If the issue keeps happening, check the Base44 Discord for known issues or contact support with details about the error.