PANGOLIN_SETUP_TOKEN can't be set on initial deployment #306

Closed
opened 2026-04-05 17:05:42 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @8de2fdb0 on 1/28/2026

Describe the Bug

when setting PANGOLIN_SETUP_TOKEN on initial server start server crashes

Overwriting existing token in DB since PANGOLIN_SETUP_TOKEN is set
Failed to ensure setup token: TypeError: Cannot read properties of undefined (reading 'tokenId')
    at ensureSetupToken (/app/server/setup/ensureSetupToken.ts:75:66)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async runSetupFunctions (/app/server/setup/index.ts:10:5)
    at async startServers (/app/server/index.ts:35:5)
TypeError: Cannot read properties of undefined (reading 'tokenId')
    at ensureSetupToken (/app/server/setup/ensureSetupToken.ts:75:66)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async runSetupFunctions (/app/server/setup/index.ts:10:5)
    at async startServers (/app/server/index.ts:35:5)

Running following sql query and restarting the service fixes it:

insert into "setupTokens" values ('8afa9ce2e0866e4','initialDataBaseToken', false, extract(epoch from now())::bigint::text, null);

So the env variable is either not intended to be used on first start or there is a logic error.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04)
  • Pangolin Version: postgresql-1.15.1
  • Gerbil Version: NONE
  • Traefik Version: UNRELATED
  • Newt Version: UNRELATED
  • Olm Version: (if applicable) UNRELATED

To Reproduce

Start a fresh service on an empty DB injecting some valid PANGOLIN_SETUP_TOKEN into env.

Expected Behavior

I don't know. I personally would expect that token to be pushed into the database and thats it.

Also a bit straingh to hold it into the DB if you ever need one and don't want to keep it around ?

Wouldn't it be easier just read it from env, or generate it if user table or what ever is empty and then forget about it?

*Originally created by @8de2fdb0 on 1/28/2026* ### Describe the Bug when setting PANGOLIN_SETUP_TOKEN on initial server start server crashes ```bash Overwriting existing token in DB since PANGOLIN_SETUP_TOKEN is set Failed to ensure setup token: TypeError: Cannot read properties of undefined (reading 'tokenId') at ensureSetupToken (/app/server/setup/ensureSetupToken.ts:75:66) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async runSetupFunctions (/app/server/setup/index.ts:10:5) at async startServers (/app/server/index.ts:35:5) TypeError: Cannot read properties of undefined (reading 'tokenId') at ensureSetupToken (/app/server/setup/ensureSetupToken.ts:75:66) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async runSetupFunctions (/app/server/setup/index.ts:10:5) at async startServers (/app/server/index.ts:35:5) ``` Running following sql query and restarting the service fixes it: ```sql insert into "setupTokens" values ('8afa9ce2e0866e4','initialDataBaseToken', false, extract(epoch from now())::bigint::text, null); ``` So the env variable is either not intended to be used on first start or there is a logic error. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: postgresql-1.15.1 - Gerbil Version: NONE - Traefik Version: UNRELATED - Newt Version: UNRELATED - Olm Version: (if applicable) UNRELATED ### To Reproduce Start a fresh service on an empty DB injecting some valid PANGOLIN_SETUP_TOKEN into env. ### Expected Behavior I don't know. I personally would expect that token to be pushed into the database and thats it. Also a bit straingh to hold it into the DB if you ever need one and don't want to keep it around ? Wouldn't it be easier just read it from env, or generate it if user table or what ever is empty and then forget about it?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#306