[Tech debt] netbird: serve via trusted HTTPS so it works in the iframe (no cert warning) #56

Closed
opened 2026-06-17 22:08:52 +00:00 by lfg2025 · 0 comments
Owner

Follow-up from #15 (option B). netbird's dashboard now works over a self-signed HTTPS cert, but that means: (a) the user accepts a browser cert warning once, and (b) it can't be embedded in the archipelago iframe — a self-signed-HTTPS frame is blocked with no way to accept the cert inside it, so netbird is forced to "open in new tab".

Goal: serve netbird behind the archipelago system's existing trusted HTTPS (same cert/origin as the main UI) instead of a per-app self-signed cert, so there's no warning and it works embedded in the iframe. Likely part of the netbird→registry-app migration (#52): proper reverse-proxy/subpath or a trusted cert provisioned for the app.

Until then, option A ships: netbird = HTTPS self-signed + open-in-new-tab.

Follow-up from #15 (option B). netbird's dashboard now works over a **self-signed** HTTPS cert, but that means: (a) the user accepts a browser cert warning once, and (b) it **can't be embedded in the archipelago iframe** — a self-signed-HTTPS frame is blocked with no way to accept the cert inside it, so netbird is forced to "open in new tab". **Goal:** serve netbird behind the archipelago system's *existing trusted* HTTPS (same cert/origin as the main UI) instead of a per-app self-signed cert, so there's no warning and it works embedded in the iframe. Likely part of the netbird→registry-app migration (#52): proper reverse-proxy/subpath or a trusted cert provisioned for the app. Until then, option A ships: netbird = HTTPS self-signed + open-in-new-tab.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfg2025/archy#56
No description provided.