-
-
Notifications
You must be signed in to change notification settings - Fork 704
bug: Cannot Deploy on Self Hosted Instance #1645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For now use the Btw, the Coolify template they provide has issues (it's not created by us, it's unofficial). So you might want to read this too: https://github.com/Mortalife/trigger-dev-coolify/blob/main/docker-compose.yml |
Same issue, what the heck this and we have to do with coolify? @matt-aitken 👀 |
BTW, I downgraded to 3.3.11 but same error. Is there a way for me to fix it anyhow until you release it?
|
I, too, am getting the same error. I'm on MacOS 15.1.1. (M1) I see it builds and pushes up to docker, but the self-hosted version still seems to think the deployment failed. I'm running:
Here is the logs:
|
That is not 3.3.11 you are running. You need to run the CLI like this: npx [email protected] deploy |
That worked! Forgive me. I thought I had to downgrade '@trigger.dev/sdk' Thank you so much @matt-aitken that unblocked me! 🙏 |
No problem! Glad you got it working :) |
Provide environment information
System:
OS: macOS 15.3
CPU: (11) arm64 Apple M3 Pro
Memory: 96.70 MB / 18.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.9.0 - /opt/homebrew/bin/node
npm: 10.8.3 - /opt/homebrew/bin/npm
Describe the bug
I just installed Trigger.dev using Coolify (Docker Installation) and with a custom Docker-Registry and everything is working fine, including the local dev mode.
But when I try to do the
npx trigger.dev@latest deploy --self-hosted --push
the build fails sayingError: 500 Unexpected Server Error. Full build logs have been saved to /tmp/trigger-nzgjKE/build-gkrpbbhq.log
The same is true when doing it in the Github Action using the official Trigger.dev docs GitHub Actions template.
The mentioned log file does not contain any information on the error at all. It just ends by telling that all the layers have been pushed to the docker registry successfully.
But in the logs of the trigger docker container, there is an error message, which I have provided in the "Additional information" field.
Reproduction repo
Sadly a private project, but happens on all repos
To reproduce
Additional information
The text was updated successfully, but these errors were encountered: