Fix manage-server crash-loop: generate and pass through TRITON_MANAGE_JWT_SIGNING_KEY #16
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
primatekuntech/triton-install!16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/jwt-signing-key-generation"
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?
Fixes #15
Fresh installs crash-loop because the server requires
TRITON_MANAGE_JWT_SIGNING_KEYbut nothing ever generated it, and even setting it by hand in.envdidn't help sincecompose.yamldidn't forward it into the container.install.sh: generate the key alongsideTRITON_VAULT_KEY/TRITON_MANAGE_WORKER_KEYon first installenv.template: add the placeholdercompose.yaml: add the var tomanage-server's environment whitelist so it actually reaches the containerupgrade.sh: backfill the key for existing.envfiles that predate this fixVerified live on a fresh Ubuntu 24.04 VPS install (
--no-tlsbehind Caddy) — container now starts healthy and/api/v1/healthreturns 200.