The bus presents the mesh's own certificate, which names nothing a public verifier accepts; the controller's NATS client verified by name and failed against a bus that was answering — "certificate is not valid for any names, but wanted to match …" (2026-09-28). It now pins the leaf's fingerprint from MESH_BROKER_CERTIFICATE, exactly as every host does (design 25 §4).
And a connection error named the whole URL, password included; the address alone now. That error was printed once tonight, so the controller's credential is rotated with rollout mint --again as the last step of the move.
The bus presents the mesh's own certificate, which names nothing a public verifier accepts; the controller's NATS client verified by name and failed against a bus that was answering — "certificate is not valid for any names, but wanted to match …" (2026-09-28). It now pins the leaf's fingerprint from `MESH_BROKER_CERTIFICATE`, exactly as every host does (design 25 §4).
And a connection error named the whole URL, password included; the address alone now. That error was printed once tonight, so the controller's credential is rotated with `rollout mint --again` as the last step of the move.
The bus presents the mesh's own certificate, which names nothing a public verifier
accepts; the client verified by name and failed against a bus that was answering
("certificate is not valid for any names", 2026-09-28). It now pins the leaf's
fingerprint from MESH_BROKER_CERTIFICATE, as every host does. And a connection
error named the whole URL, password included — the address alone now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The bus presents the mesh's own certificate, which names nothing a public verifier accepts; the controller's NATS client verified by name and failed against a bus that was answering — "certificate is not valid for any names, but wanted to match …" (2026-09-28). It now pins the leaf's fingerprint from
MESH_BROKER_CERTIFICATE, exactly as every host does (design 25 §4).And a connection error named the whole URL, password included; the address alone now. That error was printed once tonight, so the controller's credential is rotated with
rollout mint --againas the last step of the move.The bus presents the mesh's own certificate, which names nothing a public verifier accepts; the client verified by name and failed against a bus that was answering ("certificate is not valid for any names", 2026-09-28). It now pins the leaf's fingerprint from MESH_BROKER_CERTIFICATE, as every host does. And a connection error named the whole URL, password included — the address alone now.