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.

Milan Surelia Milan Surelia Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems. Expertise: 💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web. 🖋️ Sharing insights through technical writing, blogging, and open-source contributions. 🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences. Notable Achievements: 🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX. 🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development. 🌟 Open source contributions on Github & StackOverflow for Flutter & Dart 🎖️ Worked on improving app performance and user experience with smart solutions. Milan is always happy to connect, work on new ideas, and explore the latest in technology. Simon A. Simon A. I'm a backend developer building APIs, emulators, and interactive game systems. Professionally, I've developed Java/Spring reporting solutions, managed relational and NoSQL databases, and implemented CI/CD workflows. Jaime Orts-Caroff Jaime Orts-Caroff I'm a Senior Android developer, open to work in various fields MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. Yovel Cohen Yovel Cohen I got a lot of experience in building Long-horizon AI Agents in production, Backend apps that scale to millions of users and frontend knowledge as well. 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. Anthony Akpan Anthony Akpan Developer with 8 years of experience building softwares fro startups Caio Rodrigues Caio Rodrigues I'm a full-stack developer focused on building practical and scalable web applications. My main experience is with **React, TypeScript, and modern frontend architectures**, where I prioritize clean code, component reusability, and maintainable project structures. I have strong experience working with **dynamic forms, state management (Redux / React Hook Form), and complex data-driven interfaces**. I enjoy solving real-world problems by turning ideas into reliable software that companies can actually use in their daily operations. Beyond coding, I care about **software quality and architecture**, following best practices for componentization, code organization, and performance optimization. I'm also comfortable working across the stack when needed, integrating APIs, handling business logic, and helping transform prototypes into production-ready systems. My goal is always to deliver solutions that are **simple, efficient, and genuinely useful for the people using them.** 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. PawelPloszaj PawelPloszaj I'm fronted developer with 10+ years of experience with big projects. I have small backend background too

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