> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cli/help/troubleshooting.md). # Troubleshooting Fix Devolutions CLI problems by what you see: sign-in errors, references that don't resolve, unsupported commands and the background process. Find what you're seeing below. Each page lists the causes, most frequent first, and how to fix them.


Sign-in fails or the session expired	`devo login` fails, or a command that worked yesterday asks you to sign in again.	Sign-in fails or the session expired
A secret reference doesn't resolve	`invalidSecretReference`, an entry or a field that can't be found, or a reference that points at another workspace.	A secret reference doesn't resolve
A command says the workspace doesn't support it	`operationNotSupportedBySource`, or a command that's only for Devolutions Cloud or Devolutions Server.	A command says the workspace doesn't support it
The background process won't start	`daemonUnavailable`, `daemonTimeout`, or a command that hangs before it does anything.	The background process won't start

Have a quick question instead? See the [frequently asked questions](/cli/help/troubleshooting/faq.md). ## Read the error first Every error has a **code** and a **message**. In a terminal, Devolutions CLI writes them on one line, for example: ``` confirmationRequired: Pass --yes to delete the entry. ``` The code is stable, so it's what you search for in this documentation or test in a script. With `--output json`, the error comes as a JSON document instead, with the code and message in its `errors` list. See [Read results as JSON](/cli/for-devops-and-administrators/automate/json-output.md). The exit code also tells you what kind of problem it is:

EXIT CODE	MEANING
`2`	The command line was refused before anything happened: a typo, a missing option, or a change without `--yes`.
`1`	The command ran but failed, for example because the selected workspace doesn't support it.
`3`	The background process or the workspace couldn't complete the request.
`4`	A vault, entry, user, or group wasn't found.
`130`	You interrupted the command.

The complete list is in [Exit codes and errors](/cli/reference/exit-codes-and-errors.md). ## Still stuck? [Collect diagnostics](/cli/help/troubleshooting/collect-diagnostics.md) and contact [Devolutions support](https://devolutions.net/support/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/cli/help/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.