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.

Victor Denisov Victor Denisov Developer Basel Issmail Basel Issmail ’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems. My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale. In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals. I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software. Nam Tran Nam Tran 10 years as fullstack developer Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : ) Franck Plazanet Franck Plazanet I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth. Core Expertise: 🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement. 🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure. ☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs. 📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue. I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity. Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever Vlad Temian Vlad Temian 15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox). Cursor ambassador and agentic tooling builder. I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti. I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks. https://blog.vtemian.com/ Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. legrab legrab I'll fill this later AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies.

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