Editor and Dashboard
Unable to access the landing page of my app
Unable to access the landing page of my app
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.For more on privacy settings, see the Authentication guide.
- Go to your app’s dashboard.
- Click Overview.
- Under App Visibility, select Public.
- Create a separate app for your public landing page.
- Publish both apps.
- Link this landing app to your main, private app.
- 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.
The screen is white when I click on something in my app
The screen is white when I click on something in my app
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:
- Click Revert this to restore your app to a previous working version.
- 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.
- Try describing your problem to AI chat with more specific details, such as exactly where, when, and how the issue appears.
Error message: "Failed to load app: Error serializing to JSON: UnicodeEncodeError"
Error message: "Failed to load app: Error serializing to JSON: UnicodeEncodeError"
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.
AI Credits
Using too many credits when chatting with the AI
Using too many credits when chatting with the AI
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:
- Click Discuss in the AI chat window before you start chatting. The Discuss button should be highlighted.
- Plan, ask questions, and talk through your ideas with the AI.
- 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.
**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.
Data and Security
Row-level security (RLS) is not restricting data access correctly
Row-level security (RLS) is not restricting data access correctly
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:
- Go to your app’s dashboard and click Security.
- Click Start security check to scan for missing or misconfigured RLS rules.
- Review the issues found and click Apply Fixes to use the recommended safe defaults, or adjust rules for each data entity manually.
- Sign in with different user roles to confirm only authorized people can access each type of data.
Performance and Speed
Error 500 appears when loading, saving, or using your app
Error 500 appears when loading, saving, or using your app
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:
- Refresh the page or try again later, as some 500 errors are temporary.
- Check the status page or Discord channels to see if there is a known platform incident.
- Your app name
- Where and when the error happens
- Any error messages from the console (screenshots if possible)
- What steps led to the problem
App does not load or shows a blank/white screen
App does not load or shows a blank/white screen
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.
- Refresh the page or open the app in a new browser window.
- Clear your browser cache and cookies, then try loading again.
- Make sure your internet connection is stable.
- Switch browsers or devices to see if the issue persists elsewhere.
- If you made recent edits before the issue started, try reverting your most recent changes if possible.
- Wait a few minutes. Sometimes the platform is updating or experiencing temporary downtime.
- 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)
If you’re stuck in an infinite loading state after using all your credits or after a large edit, mention this in your message.
Tailwind CDN script is injected by the platform and cannot be removed
Tailwind CDN script is injected by the platform and cannot be removed
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 returning 404 errors at public URLs
Backend functions are returning 404 errors at public URLs
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.
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:
Step 1 | Test your backend function
Step 1 | Test your backend function
- Click Dashboard in your app editor.
- Click Code.
- Click Functions.
- Select the relevant function.
- Click Test Function at the bottom right.
- (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.
Step 2 | Troubleshooting persistent 404 errors
Step 2 | Troubleshooting persistent 404 errors
- Confirm your plan supports backend functions: Make sure you are on a Base44 plan that includes backend function support, such as the Builder tier.
- Check backend functions are enabled: Go to your app settings in the Base44 dashboard and verify backend functions are enabled.
- 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().
- Redeploy your app: Redeploy from the dashboard to trigger a fresh deployment and update app routing.
- Review recent build and deployment: If your app was recently updated, check that all build and deployment steps completed successfully.
- 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.
Base44 unable to fetch API key
Base44 unable to fetch API key
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:
- Log in to the service.
- Go to the API or developer section.
- Generate your key.
- Paste it into Base44 as a Secret.
Domains
Domain is stuck in 'Pending'
Domain is stuck in 'Pending'
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:
- Remove any AAAA (IPv6) records for your domain, as these can interfere with proper setup.
- Wait 48–72 hours for changes to fully propagate across the internet.
- Use a tool like whatsmydns.net to confirm your updated records are visible globally.
- Double-check that you entered the exact record values.
- If the status is still pending after about 30 minutes, try unlinking the domain in Base44, then re-adding it.
- A screenshot of your DNS records
- Your domain name
- Your Base44 app link
Domain from Base44 is not connecting
Domain from Base44 is not connecting
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:
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:
- Open the IONOS email and click the link to confirm your email address.
- In Base44, go to your app’s Dashboard and click Domains, select the domain, and click Unlink domain.
- Connect the domain again.
- Wait a few minutes for the connection to complete.
Domain is stuck in 'Connecting'
Domain is stuck in 'Connecting'
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.
Domain is connected but it is not working and the site is not loading
Domain is connected but it is not working and the site is not loading
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.
SSL setup issues or ERR_SSL_PROTOCOL_ERROR after connecting a custom domain
SSL setup issues or ERR_SSL_PROTOCOL_ERROR after connecting a custom domain
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.
- A screenshot of your current DNS records
- Your domain name
- A link to your Base44 app
Unable to connect a domain to a new app after deleting the previous app
Unable to connect a domain to a new app after deleting the previous 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.
Did not receive the domain verification email after purchasing a domain from Base44
Did not receive the domain verification email after purchasing a domain from Base44
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:
- Check your inbox, spam, and junk folders for an email from IONOS.
- If you cannot find the email, contact IONOS (the domain registrar) and request a new verification email.
- When you contact IONOS, provide your domain name and explain that you have not received the verification email after purchasing your domain.
- Follow the steps from IONOS to complete your domain verification.
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
Unable to upload videos
Unable to upload videos
Uploading videos 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.
Error message: Invalid MIME type. Only image types are supported
Error message: Invalid MIME type. Only image types are supported
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:
- Check that your file is one of the supported formats:
- Images: PNG, JPG, or JPEG
- Docs: PDF, TXT, or HTML (where allowed)
- Make sure your file does not exceed the size limits set by Base44.
- If you accidentally uploaded a wrong file, click Revert this to undo the last step.
- Try uploading your file again using a supported format.