[Tech debt] netbird: serve via trusted HTTPS so it works in the iframe (no cert warning) #56
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.