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.

prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Jen Jacobsen Jen Jacobsen I’m a Full-Stack Developer with over 10 years of experience building modern web and mobile applications. I enjoy working across the full product lifecycle — turning ideas into real, well-built products that are intuitive for users and scalable for businesses. I particularly enjoy building mobile apps, modern web platforms, and solving complex technical problems in a way that keeps systems clean, reliable, and easy to maintain. Pratik Pratik SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture 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. PawelPloszaj PawelPloszaj I'm fronted developer with 10+ years of experience with big projects. I have small backend background too Tejas Chokhawala Tejas Chokhawala Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript. Focused on performance, clean architecture and shipping fast. Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools. Victor Denisov Victor Denisov Developer Nam Tran Nam Tran 10 years as fullstack developer Matt Butler Matt Butler Software Engineer @ AWS

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