Fix manage-server crash-loop: generate and pass through TRITON_MANAGE_JWT_SIGNING_KEY #16

Merged
amiryahaya merged 1 commit from fix/jwt-signing-key-generation into main 2026-08-13 07:53:08 +02:00
Owner

Fixes #15

Fresh installs crash-loop because the server requires TRITON_MANAGE_JWT_SIGNING_KEY but nothing ever generated it, and even setting it by hand in .env didn't help since compose.yaml didn't forward it into the container.

  • install.sh: generate the key alongside TRITON_VAULT_KEY/TRITON_MANAGE_WORKER_KEY on first install
  • env.template: add the placeholder
  • compose.yaml: add the var to manage-server's environment whitelist so it actually reaches the container
  • upgrade.sh: backfill the key for existing .env files that predate this fix

Verified live on a fresh Ubuntu 24.04 VPS install (--no-tls behind Caddy) — container now starts healthy and /api/v1/health returns 200.

Fixes #15 Fresh installs crash-loop because the server requires `TRITON_MANAGE_JWT_SIGNING_KEY` but nothing ever generated it, and even setting it by hand in `.env` didn't help since `compose.yaml` didn't forward it into the container. - `install.sh`: generate the key alongside `TRITON_VAULT_KEY`/`TRITON_MANAGE_WORKER_KEY` on first install - `env.template`: add the placeholder - `compose.yaml`: add the var to `manage-server`'s environment whitelist so it actually reaches the container - `upgrade.sh`: backfill the key for existing `.env` files that predate this fix Verified live on a fresh Ubuntu 24.04 VPS install (`--no-tls` behind Caddy) — container now starts healthy and `/api/v1/health` returns 200.
install.sh generated TRITON_VAULT_KEY and TRITON_MANAGE_WORKER_KEY but never
TRITON_MANAGE_JWT_SIGNING_KEY, which the server requires to start. Even when
set manually, compose.yaml didn't forward it into the container since its
environment block explicitly whitelists every passed-through variable.

- install.sh: generate the key alongside the other auto-generated secrets
- env.template: add the placeholder so first-run install.sh can fill it
- compose.yaml: add the var to manage-server's environment whitelist
- upgrade.sh: backfill the key into .env files from before this fix

Fixes #15
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
primatekuntech/triton-install!16
No description provided.