railway loginGitLab CI/CD Deployment
2 years ago
Following the steps outlined in the Railway documentation for GitLab CI/CD (https://blog.railway.app/p/gitlab-ci-cd), I have configured the pipeline accordingly. However, during the deployment process, I encountered the following error:
"Unauthorized. Please login with railway login"
This error message suggests that Railway authentication failed, even though Railway is successfully installed in the CI/CD environment.
ps : my .gitlab-ci.yml written same as the exemple on the docs
Your help in resolving this matter would be greatly appreciated.
18 Replies
2 years ago
The team is aware, there are some permission issues around the project token, I'll update you when I have more information.
In the mean time, your code is still uploaded and a build will still go out.
a year ago
is this still an issue?
a year ago
I'm facing the same issue when deploying using gitlab ci. Doesnt seem like this is fixed.
Status changed to Open Railway • 12 months ago
a year ago
Same here
9 months ago
Same here
7 months ago
same here
7 months ago
is this fixed? i am experiencing the same issue on github actions
7 months ago
Same here
6 months ago
bump
5 months ago
Hi, I have exactly the same issue? can this be fixed?
Currently there is no way to create the Postgre database using both Personal Access Token or Project Access Token..
5 months ago
bump
5 months ago
I am having the same issue. Created a PAT, added as secret variable in github actions, then tried to login... no luck
thereis
I am having the same issue. Created a PAT, added as secret variable in github actions, then tried to login... no luck
5 months ago
same, i cant use the pipeline to create postgre db and enable domain, cant even login with cli
4 months ago
An important issue pending since years? Facing same p\issue. Please fix.
2 months ago
Facing the same issue, using it in github actions, it says
Unauthorized. Please check that your RAILWAY_TOKEN is valid and has access to the resource you're trying to use.
a month ago
Same here
a month ago
This has been resolved, if you are still seeing this error please make sure you are using the token that is correctly scoped to the resources you are trying to use.
Status changed to Solved brody • about 1 month ago