Help and fixes
Get unstuck fast. Every entry starts with what you see in the Marshal web app or CLI, then gives the cause and the fix. Error text is quoted exactly as Marshal shows it, so you can search for it. When a fix needs an admin, the entry says what the admin checks.
Most common
- A request is blocked by network policy
- Launch is disabled until credentials are added
- A connection needs to be reconnected
- A space fails to start
- The run waits for an answer
- The CLI is not logged in
Pick an area
| Area | Use it when |
|---|---|
| Signing in and access | You cannot sign in, an invitation fails, or a button is missing for your role. |
| Spaces | A space will not start, stop, or launch from a manifest. |
| Runs and deputies | A run fails, times out, waits, or ends with an unexpected status. |
| Credentials and integrations | A credential will not save, GitHub refuses a push, or Slack or Atlassian calls fail. |
| Marketplace and packages | A package will not install, a new version does not reach your spaces, or a build tool is missing. |
| Webhooks | A delivery does not arrive, is refused, or starts no mission. |
| MCP servers | An MCP package will not connect or lacks a tool. |
| Network and egress | A host is blocked or a network policy cannot be deleted. |
Before you dig in
- Reload the page to see the latest state.
- Check the exact text of the error. Most entries here are matched by text.
- If you run the Marshal install yourself, see Troubleshooting for images, ingress and storage.
Related
- Reference for CLI commands, roles and the package catalog
- Configuration reference for the settings an operator controls