MultiConnectSDK › CLI
14. Troubleshooting
| Message or problem | What it means | What to do |
|---|---|---|
Invalid or expired access key |
The key is wrong or has expired | Check it under Access Keys, then run multiconnect init --force |
not attached, or Unknown deployment |
The key is not attached to this deployment | Attach it on the deployment's page on the dashboard |
cannot deploy |
The key does not have Allow deploys (CLI) on | Create a key with it on, and link again |
A … is already in progress |
Another rollout or change is running | Wait for it, and check with multiconnect status |
old containers are still in their grace period |
The last rollout's old servers are still draining | Wait, or release them early on the dashboard |
has no build to deploy |
This folder is linked to a database | Link the folder to a server, API or website |
Timestamp is outside the 5-minute window |
Your computer's clock is wrong | Correct the clock |
--config needs an interactive terminal |
You ran --config in CI or a script |
Run it in your own terminal, or use the dashboard |
| Rolled back | The new build never became healthy | Check that it listens on the port it is given, and read the logs on the dashboard |
Build directory not found |
The build path does not exist | Run your build, or check the path in multiconnect.json |
No access key |
This machine has no stored key | Set MC_ACCESS_KEY and MC_ACCESS_SECRET, or run multiconnect init |
cannot be read by this user |
The stored key was saved by another login on this computer | Run multiconnect init again, or set the two variables |
has not been approved on this machine |
The build command is new here, and nobody was asked | Check the command in multiconnect.json, then run in your terminal, or add --approve-build-command in CI |
outside this project folder |
The build path points outside the folder | Set a build path inside the project with multiconnect deploy --config |
--secret is not accepted |
The secret was given on the command line | Set MC_ACCESS_SECRET, or run multiconnect init and enter it when asked |
multiconnect is not recognised |
The .NET tools folder is not on your PATH | Open a new terminal. If it still fails, add ~/.dotnet/tools to your PATH |

