The MongoDB connection string is empty or wrong

What it means

The address of MongoDB is not set or does not start with mongodb:// or mongodb+srv://.

The build passed, but the app did not start or did not answer the health check.

Typical causes

• The app does not listen on 0.0.0.0 and the port from the PORT variable
• An environment variable is missing, or the database or Redis is not connected
• The start command is wrong or the process exits right away

How to fix it on mevcore

Check the variable the application reads (MONGODB_URI, MONGO_URL, DATABASE_URL) on the «Environment» tab; special characters in the password must be URL-encoded.

1. 1 Open the app in the mevcore panel: the Problems card on the overview shows this error and the log line it was found in.
2. It is fixed on the “Environment” tab of the app.
3. 2 After the fix, deploy again. If it fails again, the log ends with [mevcore] lines naming the new error code.
4. 3 The "Ask AI" button next to the error prepares a request for ChatGPT or Claude: the error code, the end of the log without secrets and the app settings.

For an AI assistant

The same in English: paste it together with the log into the AI chat.

mevcore error code: runtime.mongo_uri_invalid
phase: start / health check
diagnosis: The MongoDB connection string is empty or wrong
platform hint: The address of MongoDB is not set or does not start with mongodb:// or mongodb+srv://. Check the variable the application reads (MONGODB_URI, MONGO_URL, DATABASE_URL) on the «Environment» tab; special characters in the password must be URL-encoded.
platform docs: https://mevcore.com/llms-full.txt

Related errors

• runtime.laravel_mac_invalid Laravel cannot decrypt data (APP_KEY changed)
• runtime.mongo_atlas_ip MongoDB Atlas does not allow connections from the node
• runtime.mongo_auth MongoDB rejected the login or password
• install.package_json_invalid package.json (or composer.json) is not valid JSON