TVO-FORGE-101: The Forge cannot serve: a component could not be opened

If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

Why it happened

In the catalog's worked example, TOVIO explains it like this. Names and values in it are illustrative.

A durable store, the runtime or a listener refused to open; the message names it and its own error.

How to fix it

1. Check storage_dir: it must exist, be a plain directory, be writable by the Forge's user, and have free space
2. If a listener is named, check the bind address is free and permitted

What TOVIO prints

The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative, and the command exits with status 1.

✗ The Forge cannot serve: the proposal store could not be opened

  cause: permission denied
  Check `storage_dir`, its permissions and its free space, then start the Forge again.
  [TVO-FORGE-101]

What to read

• Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-FORGE-101 is in the FORGE area and carries the same three-part message either way.
• Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.

Still stuck, or is the message wrong?

Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.

Report this error

All error codes