Operator guide for Valet Dedicated 0.10.1

Get help

Valet has no access to your installation and receives nothing from it. Support works from what you send.

Contact

Email support@valet.dev.

Valet answers within one business day. An outage that stops your installation gets an answer within four business hours. Say "outage" in the subject.

Before you write, try Troubleshoot. It covers the failures operators meet most.

What to send

Build a support bundle and send it:

$VD support bundle --out ./valet-support

The bundle is a directory. It holds your installation's descriptor, the result of check, the last five deployment records, each service's recent events and stopped tasks, the last hour of each service's log, and your system settings. A secret setting shows only set or unset. manifest.json lists every file, what it holds, and what the tool removed.

Valet receives nothing until you send it. The command uploads nothing.

  1. Open the directory and read every file. The tool removes values that look like secrets and replaces each with [redacted]. It cannot know every secret, so your review is the last check.
  2. Zip the directory and email it to support@valet.dev.
  3. Add the command that failed and its full output, if the problem follows one.
  4. Add the deployment record key that upgrade printed, if the problem follows an upgrade.

If a permission is missing, the bundle says so in manifest.json and writes the rest. Re-apply the module to grant it, then build the bundle again.

Add --since 3h to read more of the logs. Each log file holds at most 5 MB and keeps the newest lines. The manifest marks a file it cut.

To send only the check, run it with JSON output. The first lines name the installation, the region, and whether every item passed:

$VD check --output json

What not to send

Never send secret values, the operator token, or API keys. That includes the WorkOS API key and the Anthropic API key. If a command's output holds one, remove it before you send.