Relays: each relay's certificate #149

Merged

jcoffey-dev merged 1 commits from relay/certificate-error into main

2026-10-30 23:27:31 +00:00

jcoffey-dev commented

2026-10-30 22:24:00 +00:00

Owner

Each relay's certificate on the Relays page (relay spec, RL-27; inbuxa-server #269).

The list says when a joined relay has no certificate, when this server couldn't order one (with the reason), and when it runs out. The expiry comes from the certificate stored here, or else from the one the relay reports. A server from before #269 sends none of this, so no new line shows.
The relay's settings get a Certificate section. It says how long the certificate is good for, or why the last order failed. Where no domain here manages the public name's DNS, the chain and key can be pasted there. The key is never shown, and leaving it empty keeps the stored one. Clearing the chain removes both.
Help texts for the chain and the key.

Checks: typecheck, lint, i18n:check, 966 tests (one new, for the certificate lines), build, notice-check.

Preview: the Chrome extension wasn't connected, so I didn't look at the page in a browser. Against a local server built from #269, I sent over JMAP the same update the dialog sends: a pasted self-signed chain and key. certificateNotAfter then read its expiry, the key read back as ****, and clearing both removed them.

Each relay's certificate on the Relays page (relay spec, RL-27; inbuxa-server #269). - **The list** says when a joined relay has no certificate, when this server couldn't order one (with the reason), and when it runs out. The expiry comes from the certificate stored here, or else from the one the relay reports. A server from before #269 sends none of this, so no new line shows. - **The relay's settings** get a Certificate section. It says how long the certificate is good for, or why the last order failed. Where no domain here manages the public name's DNS, the chain and key can be pasted there. The key is never shown, and leaving it empty keeps the stored one. Clearing the chain removes both. - Help texts for the chain and the key. Checks: typecheck, lint, i18n:check, 966 tests (one new, for the certificate lines), build, notice-check. Preview: the Chrome extension wasn't connected, so I didn't look at the page in a browser. Against a local server built from #269, I sent over JMAP the same update the dialog sends: a pasted self-signed chain and key. `certificateNotAfter` then read its expiry, the key read back as `****`, and clearing both removed them.

jcoffey-dev added 1 commit 2026-10-30 22:24:00 +00:00

Relays: each relay's certificate

ci / build (pull_request) Skipped

Details

ci / publish (pull_request) Skipped

Details

ci / notices (pull_request) Successful in 18s

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 1m21s

Details

d5eeb4a104

The list says when a joined relay has no certificate, when this server
couldn't order one and why, and when it runs out, from the certificate
stored here before the one the relay reports (relay spec, RL-27). A
server from before RL-27 sends none of this, and no line shows.

A relay's settings get a Certificate section: how long it's good for or
why the last order failed, and the chain and key to paste where no
domain here manages the public name's DNS. The key is never shown;
left empty, the stored one stays. Clearing the chain removes both.

jcoffey-dev merged commit fe11f63997 into main

2026-10-30 23:27:31 +00:00

jcoffey-dev deleted branch relay/certificate-error

2026-10-30 23:27:31 +00:00

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-admin#149