a year ago
Hi Railway Team, actually encountering and still getting the same issue as previous deployment, an issue that block my pipeline to deploy my backend app but i've no possibility to redeploy it from not corrupted version. Can you help me with that deploy issue. Thanks in advance, Maxime Pietrucci-Blacher
My pipeline :
Run railway up --service ***
railway up --service ***
shell: /usr/bin/bash -e {0}
env:
GITHUB_REPO_NAME: UrEsport/***
RAILWAY_TOKEN: ***
Error: Process completed with exit code 1.
And i can't deploy it manually too without getting debug traces
5 Replies
Status changed to Awaiting User Response Railway • about 1 year ago
brody
Hello,Can you please provide the error printout from the CLI?
a year ago
Hello, everything goes well in terms of deployment when I use the CLI manually but however when I make my CI (token + serviceId) it does not work at all, I also took the time to regenerate the credentials several times but without success.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Will need some errors with this one. The tokens are kinda in an annoying state right now where we have both RAILWAY_TOKEN and also RAILWAY_API_TOKEN (for personal and workspace tokens respectively)
Please make sure you're using the right one from the documentation
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
Hello, I'm currently using a project token that I've tried several times to regenerate in order to fix the issue, but nothing works and I don't have any logs in the debug mod output (github actions) that allow me to know where it is. Attached is the CD debug file and the associated workflow.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
I'm going to open this up to the community as I'm not certain what's going on here
However, we use the CLI tokens for Railway, so they are currently working as intended
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open jake • about 1 year ago