Base44 deployment

Environment Variables or Secrets Not Available in Published Base44 App

Your Base44 app uses environment variables or secret keys (for API integrations, database connections, or third-party services), but these values are not available in the published version of the app. Features that depend on these variables work in the editor but fail in production.

This commonly manifests as API calls returning authentication errors, integrations silently failing, or features that depend on configuration values behaving differently in the published app.

Error Messages You Might See

API key is missing or invalid Environment variable undefined 403 Forbidden Authentication failed: missing credentials
API key is missing or invalidEnvironment variable undefined403 ForbiddenAuthentication failed: missing credentials

Common Causes

  1. Environment variables were set in the editor or preview environment but not in the production deployment settings
  2. The variable names are slightly different between environments (typo or case difference)
  3. Secrets are being exposed in client-side code instead of being used in server-side functions only
  4. The app was re-published but the environment variables were not refreshed or re-deployed

How to Fix It

Check your Base44 app's deployment or environment settings to ensure all required variables are set for the production environment, not just the preview environment. Variable names must match exactly, including case.

Ensure that sensitive keys and secrets are only accessed in server-side code or functions. If they're referenced in client-side code, they may be stripped out during the build for security reasons.

For apps with many environment-dependent integrations, a developer can audit the configuration and ensure all variables are properly set and accessible in every environment.

Real developers can help you.

Meïr Ankri Meïr Ankri Full-stack developer specializing in React / Next.js / Node.js with 6+ years of experience. I've worked across various sectors including automotive (Reezocar/Société Générale), healthcare (Medical Link SaaS), and e-commerce (Glasman). I build web apps end-to-end, from architecture to production, with a focus on scalability, performance, and code quality. I also mentor junior developers and contribute to technical decisions and code reviews. Kingsley Omage Kingsley Omage Fullstack software engineer passionate about AI Agents, blockchain, LLMs. AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies. Antriksh Narang Antriksh Narang 5 years+ Experienced Dev (Specially in Web Development), can help in python, javascript, react, next.js and full stack web dev technologies. Dor Yaloz Dor Yaloz SW engineer with 6+ years of experience, I worked with React/Node/Python did projects with React+Capacitor.js for ios Supabase expert rayush33 rayush33 JavaScript (React.js, React Native, Node.js) Developer with demonstrated industry experience of 4+ years, actively looking for opportunities to hone my skills as well as help small-scale business owners with solutions to technical problems Matthew Butler Matthew Butler Systems Development Engineer @ Amazon Web Services MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. Richard McSorley Richard McSorley Full-Stack Software Engineer with 8+ years building high-performance applications for enterprise clients. Shipped production systems at Walmart (4,000+ stores), Cigna (20M+ users), and Arkansas Blue Cross. 5 patents in retail/supply chain tech. Currently focused on AI integrations, automation tools, and TypeScript-first architectures. Matthew Jordan Matthew Jordan I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Why do my API keys work in Base44 preview but not when published?

Environment variables are often configured separately for preview and production. Check your deployment settings to ensure all variables are set for the production environment.

Are my API keys safe in Base44?

Only use secrets in server-side functions, never in client-side code. Client-side code is visible to users and may have secrets stripped during the build process.

Related Base44 Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help