TVO-FORGE-100: No TLS material; refusing to bind

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.

The resolved configuration names no TLS certificate and key, and the Forge has no plaintext mode.

How to fix it

1. Set tls_cert and tls_key in forge.toml
2. Pass --config <path> (or TOVIO_FORGE_CONFIG) naming the intended forge.toml

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.

✗ No TLS material in forge.toml — refusing to bind

  There is no plaintext mode (REQ-WIRE-002). Set `tls_cert` and `tls_key`, or pass
  `--config <path>` naming a forge.toml that does.
  [TVO-FORGE-100]

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-100 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