3 months ago
Account tokens (3 separately generated, all Account-scoped with "My Projects" workspace selected) consistently fail with "Not Authorized" on the me GraphQL query at https://backboard.railway.com/graphql/v2, despite the account being fully active (verified email, valid payment method, Admin role, dashboard/CLI login working normally).
Notably, the error code is "INTERNAL_SERVER_ERROR" rather than a standard auth rejection code, and response headers confirm the request reaches your backend (x-ratelimit-remaining present).
Trace IDs for reference: 6434087417493105168, 8294413441161635904
Could you check if there's an account-level issue preventing API token authentication?
1 Replies
3 months ago
Your workspace's subscription state is currently inactive, which is the likely cause of the API token auth failures. The Hobby plan was selected but the subscription never fully activated (the initial payment authorization was canceled, not captured). You can resolve this by visiting your billing settings and completing the subscription setup. Once the subscription is active, your API tokens should authenticate normally.
Status changed to Awaiting User Response Railway • 3 months ago
3 months 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 • 3 months ago