7 days ago
when i use this CLI command: railway login
> Open the browser? Yes
Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)
Caused by:
0: error sending request for url (https://backboard.railway.com/graphql/v2)
1: client error (Connect)
2: invalid peer certificate: UnknownIssuer
Pinned Solution
7 days ago
the issue is that your local environment (likely due to an active VPN, a corporate proxy, a tool like Cloudflare WARP, or specialized local antivirus firewalls) is intercepting the connection and replacing Railway's SSL certificate with an untrusted local one.
since the Railway CLI is strict and does not read Windows' custom certificate stores natively, we need an alternative way to authenticate and execute commands. solve this by bypassing interactive commands entirely and routing your CLI operations directly using an explicit Railway Account Token
7 Replies
7 days ago
The "invalid peer certificate: UnknownIssuer" error means your local machine's TLS stack does not trust the certificate being presented when the CLI tries to reach our servers, which typically happens when a corporate proxy, firewall, or antivirus software is intercepting HTTPS traffic and re-signing it with its own certificate. Disabling SSL inspection for Railway endpoints (or adding the intercepting proxy's CA certificate to your system trust store) would resolve this, and you can also try railway login --browserless as an alternative login method.
Status changed to Awaiting User Response Railway • 7 days ago
7 days ago
this is NOT the answer. I am not even able to use the CLI for railway link, etc . I have a feeling this is connect to what occurred earlier today with the railway logs and CLI not working
Status changed to Awaiting Railway Response Railway • 7 days ago
Status changed to Open Railway • 7 days ago
7 days ago
Im also seeing that standard railway CLI commands are not working.
exampe: railway logs --service api-server-paid
Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)
Caused by:
0: error sending request for url (https://backboard.railway.com/graphql/v2)
1: client error (Connect)
2: invalid peer certificate: UnknownIssuerPS F:\TreadCommand\Workspace\medusajs-clean-reset>
curiouskal
Im also seeing that standard railway CLI commands are not working. exampe: railway logs --service api-server-paid Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2) Caused by: 0: error sending request for url (https://backboard.railway.com/graphql/v2) 1: client error (Connect) 2: invalid peer certificate: UnknownIssuer PS F:\TreadCommand\Workspace\medusajs-clean-reset>
7 days ago
something on your machine or network is acting as a "middleman." It intercepts the secure connection to backboard.railway.com, looks at the data, and then re-signs it with its own certificate. Since the Railway CLI doesn't recognize that middleman as a trusted authority, it throws the UnknownIssuer error for security reasons.
7 days ago
check if you have a vpn active or if you're on a work/school managed network and try disabling it then run railway login again
7 days ago
the issue is that your local environment (likely due to an active VPN, a corporate proxy, a tool like Cloudflare WARP, or specialized local antivirus firewalls) is intercepting the connection and replacing Railway's SSL certificate with an untrusted local one.
since the Railway CLI is strict and does not read Windows' custom certificate stores natively, we need an alternative way to authenticate and execute commands. solve this by bypassing interactive commands entirely and routing your CLI operations directly using an explicit Railway Account Token
7 days ago
yes, you guys were right. It was Norton "SafeWeb" - it was interfering. Much appreciated.
Status changed to Solved medim • 7 days ago