MultiConnectCloud › API Deployments
16. Troubleshooting
The form will not submit
| Message | Fix |
|---|---|
Name must be between 3 and 60 characters. |
Shorten or lengthen the name |
Name may contain letters, numbers, spaces, hyphens and underscores, and must start with a letter or number. |
Remove other characters |
A deployment with this name already exists in the project. |
Pick another name |
This project already has 20 deployments, which is the maximum. |
Delete a deployment or use another project |
Select a platform. |
Choose a Platform |
Select at least one region. |
Add a region |
Exactly one selected region must be marked primary. |
Click Set as Primary on one region |
...: the <plan> plan allows at most <n> containers. |
Lower the containers, or choose a bigger plan |
'<NAME>' is set by the platform and cannot be overridden. |
Remove that variable. See Section 5 |
'<NAME>' is not a valid environment variable name. |
Use letters, numbers and underscores, not starting with a number |
'<NAME>' is defined more than once. |
Remove the duplicate |
CPU scale-down threshold must be below the scale-up threshold. |
Lower the scale-down value (memory has the same check) |
A deployment can have at most 5 access keys. |
Remove a key |
'<key>' does not have "Allow deploys (CLI)" turned on. |
Remove that key. Only keys with Allow deploys (CLI) can be attached to an API. See Section 9 |
The database must be in the same project as this API deployment. |
Link a database from this project |
The linked database is not active. |
Start the database, or pick another |
Your balance is too low to run this plan for even an hour (...). Top up first. |
Add credit. See the MultiConnectCloud Guide |
Only valid .zip files are allowed |
Upload a real .zip file |
Build is larger than the <n> MB limit on the <plan> plan. |
Make the zip smaller, or choose a plan with a larger Max Upload Size |
The start command or entry point is refused
| Message | Fix |
|---|---|
A .NET deployment's start command must begin with 'dotnet'. |
Use dotnet MyApi.dll, or leave it empty |
'<file>' is not an assembly. |
A .NET start command must run a .dll |
'<command>' is not available on the Node.js image. |
Start with node, npm, npx, yarn or pnpm |
'<command>' is not available on the Python image. |
Start with python, python3, gunicorn or uvicorn |
Start command contains a disallowed pattern '...'. |
Remove shell operators. See Section 5 |
Enter your app's .dll — the one named after your project in the publish output, for example MyApi.dll. |
.NET needs Entry Point File. Enter the DLL from your dotnet publish output |
Entry point file path cannot contain '..' or '~'. |
Use a path inside your zip |
'<file>' is not in the uploaded build. |
The file to run is not in the zip. Check the Entry Point File and Start Command against what your build contains |
The deploy rolled back
The new containers never answered GET /health with a 2xx. Check, in order:
- Click Logs and use Live tail to see what the container printed.
- Your service listens on
PORTon0.0.0.0, not onlocalhostor a fixed port of your own. - Your service has a
/healthroute that returns 2xx without needing a login. - Node.js:
package-lock.jsonis in the zip andnode_modulesis not. Python:requirements.txtis in the zip. Java: the app answers/health, not only/actuator/health. - .NET: Entry Point File names your DLL, and the platform version matches the SDK you built with.
Other problems
| Problem | Fix |
|---|---|
Start the deployment before deploying to it. |
The deployment is stopped. Click Start, then deploy |
Deployment has not been provisioned yet. Delete it instead of stopping it. |
The first deploy never finished. Delete the deployment and create it again |
Scale down to at most <n> containers per region before moving to the <plan> plan. |
Scale down first, then change plan |
Custom domain is not verified yet. |
Your CNAME record does not resolve to the target yet. Check it, wait for DNS, and click Verify again |
That domain is already in use by another deployment. |
Remove it from the other deployment first |
| Your API cannot reach its linked database | Check the database allows linked API deployments in its Network Access section, and that your connection string uses the Host shown in Linked Database |
| WebSocket connections drop | Turn Web Socket on with Update, and have clients send a ping about every 30 seconds |

