mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-14 23:22:51 +00:00
15cf4d8640
Replace the Command::new("dot") shell-out in render_dot() with a direct
FFI call to the vendored Graphviz library. Drop PNG support (SVG only).
Remove GraphFormat enum, dot_is_available() helpers, dot-related
diagnostics/doctor checks, and the graphviz install prompt. Update
OpenAPI spec to remove png format and 502 responses. Update CLI help
text, snapshot tests, and documentation.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
38 lines
1.9 KiB
Text
38 lines
1.9 KiB
Text
---
|
|
title: "Troubleshooting"
|
|
description: "Diagnosing and resolving common issues with Fabro"
|
|
---
|
|
|
|
## `fabro doctor`
|
|
|
|
The `fabro doctor` command validates your installation:
|
|
|
|
```bash
|
|
fabro doctor # Local config checks + live server diagnostics
|
|
fabro doctor --verbose # Show detailed output for each check
|
|
fabro doctor --server https://fabro.example.com:3000/api/v1
|
|
```
|
|
|
|
It checks:
|
|
- Local user config and legacy `~/.fabro/.env` warnings
|
|
- Server-reported LLM provider connectivity
|
|
- GitHub App, sandbox, and Brave Search credentials
|
|
- Server authentication and crypto configuration
|
|
|
|
## Common issues
|
|
|
|
**"No API key configured"** — Set at least one provider key with `fabro provider login` or `fabro secret set`, or export it in the server process environment. Run `fabro doctor` to verify connectivity.
|
|
|
|
**Stall watchdog timeouts** — If runs are cancelled unexpectedly, the agent may be stuck or the LLM provider may be slow. Check `FABRO_LOG=debug` output for `Agent.LlmRetry` events. Increase `stall_timeout` in the graph if needed, or add [fallback providers](/core-concepts/models) to handle outages.
|
|
|
|
**Sandbox creation failures** — For Docker: ensure the Docker daemon is running and the configured image exists. For Daytona: verify `DAYTONA_API_KEY` is set and the `gh` CLI is authenticated. For Exe: verify your SSH keys are configured for `exe.dev` and that `ssh exe.dev` connects successfully.
|
|
|
|
**Port already in use** — Change the port with `fabro server start --port 3001` or stop the conflicting process.
|
|
|
|
**SSE streams disconnecting** — If using a reverse proxy, ensure buffering is disabled and the connection timeout is long enough for workflow runs. See the [reverse proxy example](/administration/deployment#binding-and-tls).
|
|
|
|
**Run config validation errors** — Use `fabro preflight` to validate without executing:
|
|
|
|
```bash
|
|
fabro preflight run.toml
|
|
```
|