12 days ago
I have logged into Railway via Github. In Railway I see 3 projects, all of which are Hobby plan projects.
My team is on a higher tier plan and I can't access it from this account.
I just pushed an update to it from the CLI, but because of this login issue or auth issue it didn't trigger a deploy.
This is a high priority bug fix a customer is waiting on, and I'd like to get it into production ASAP.
I'm not even seeing a way to submit this as a rialway ticket, just public... hopefully someone has a suggestion.
Thanks
Alex
5 Replies
12 days ago
The account this thread is tied to is a member of only one workspace, its own personal Hobby workspace, and your team's workspace is not among the workspaces it belongs to.
Deploys to your team's projects need to come from an account that is a member of the team's workspace, so either a workspace admin on your team adds this account to it, or the deploy is run from the account that is already a member there.
Status changed to Awaiting User Response Railway • 12 days ago
Railway
The account this thread is tied to is a member of only one workspace, its own personal Hobby workspace, and your team's workspace is not among the workspaces it belongs to. Deploys to your team's projects need to come from an account that is a member of the team's workspace, so either a workspace admin on your team adds this account to it, or the deploy is run from the account that is already a member there.
12 days ago
yeah obviously. I am 99% sure this account HAS been added to the team's workspace, but there's a bug or some other issue preventing me from being able to access it
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
We checked the account you signed in with, and it currently holds a workspace membership on only one workspace: your personal Hobby one. No membership on your team's workspace is recorded for this account right now, which is why that workspace and its projects don't show up for you.
The fastest way to unblock the deploy is for an Admin of your team's workspace to open that workspace's members list and confirm this account is listed there. If it isn't, they can add it again. In the meantime, a teammate who is already a member can deploy the fix.
Status changed to Awaiting User Response Railway • 12 days ago
Railway
We checked the account you signed in with, and it currently holds a workspace membership on only one workspace: your personal Hobby one. No membership on your team's workspace is recorded for this account right now, which is why that workspace and its projects don't show up for you. The fastest way to unblock the deploy is for an Admin of your team's workspace to open that workspace's members list and confirm this account is listed there. If it isn't, they can add it again. In the meantime, a teammate who is already a member can deploy the fix.
12 days ago
nope. pretty sure i was invited.
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
We checked again just now, and this account still has a membership in only one workspace, your personal Hobby workspace. An invitation on its own does not add you to a workspace. Email invites send a link that has to be opened to join, so an invite that was never opened, or that went to a different email address than the one on this account, leaves no membership in place.
A workspace Admin on your team can check the People tab in that workspace's settings and re-send the invite or invite link to this account. For CLI deploys, the role needs to be Admin or Member, because the Deployer role can't deploy from the CLI. Until then, a teammate who is already a member can push the fix out.
Status changed to Awaiting User Response Railway • 12 days ago
5 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 5 days ago