Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Self hosting: Error: Build failed: 401 "No authorization header provided" #1629

Open
druidui opened this issue Jan 22, 2025 · 1 comment
Open

Comments

@druidui
Copy link

druidui commented Jan 22, 2025

Hi, I'm getting this issue when self hosting with Coolify (I have tried the latest versions of each package, but rolled back to see if that was the issue) - I have successfully logged in, initialised, and set my local env vars. I have had trigger.dev running locally without Coolify, but their template is a bit scuffed at the moment. Thanks

TRIGGER_ACCESS_TOKEN=tr_pat_ov.......
TRIGGER_API_URL=https://t.....
TRIGGER_SECRET_KEY=tr_dev_i.....

npx trigger.dev dev

Trigger.dev (3.3.10 -> 3.3.11)
------------------------------------------------------
│
▲  Warning: You're not running the latest CLI version, please consider updating ASAP
│
│           Current:     3.3.10
│           Latest:      3.3.11
│
│           Run latest:  npx trigger.dev@latest
------------------------------------------------------
Key: Version | Task | Run
------------------------------------------------------
○ Building background worker…
│
■  Error: Build failed: 401 "No authorization header provided"
│
│         Error: 401 "No authorization header provided"
│             at DevWorkerRuntime.initializeWorker (file:///C:/Users/node_modules/trigger.dev/dist/esm/dev/workerRuntime.js:153:19)
│             at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
│             at async updateBundle (file:///C:/Users/node_modules/trigger.dev/dist/esm/dev/devSession.js:49:13)
│             at async runBundle (file:///C:/Users/node_modules/trigger.dev/dist/esm/dev/devSession.js:119:9)
│             at async startDevSession (file:///C:/Users/node_modules/trigger.dev/dist/esm/dev/devSession.js:122:26)
│             at async startDev (file:///C:/Users/node_modules/trigger.dev/dist/esm/commands/dev.js:115:23)
│             at async devCommand (file:///C:/Users/node_modules/trigger.dev/dist/esm/commands/dev.js:55:29)
│             at async file:///C:/Users/node_modules/trigger.dev/dist/esm/commands/dev.js:31:13
│             at async file:///C:/Users/node_modules/trigger.dev/dist/esm/cli/common.js:54:28
│             at async wrapCommandAction (file:///C:/Users/node_modules/trigger.dev/dist/esm/cli/common.js:40:12)
@dsc8x
Copy link

dsc8x commented Feb 23, 2025

Had the same issue but just fixed it.

I changed two things, so not 100% which of them solved it:

1: I changed TRIGGER_PROTOCOL to https (was http before, even though I'm on https)

2: I added REGISTRY_HOST and REGISTRY_NAMESPACE env vars

Hope this helps 😊

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants