--browserless
2 months ago
Hi, I'm attempting to login to Railway via CLI. However, I get the following error:
Error logging in to CLI. Please try again with --browserless
So I attempted this. But get another error:
Browserless Login
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
So right now theres no possible way for me to login via CLI.
How can I successfully login via CLI?
Currently logged in via Github.
Attachments
8 Replies
samgordon
Are you using Safari?
2 months ago
I used Firefox. I then tried with Sudo and that triggered Safari to open and got the same result
Exact versions:
Firefox developer version – 144.0b6 (aarch64)
Safari Version 18.5 (20621.2.5.11.8)
2 months ago
I've only ever been able to get this to work on Chrome or Chromium based.
samgordon
I've only ever been able to get this to work on Chrome or Chromium based.
2 months ago
I tried Chrome just now. The login noted it was successful. However, when I navigate back to VSCode I get
> 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
2 months ago
Are you using any VPN or modified firewall? Works totally fine for me.
samgordon
Are you using any VPN or modified firewall? Works totally fine for me.
2 months ago
I'm on a work device that uses Zscaler. That's all I can think of
2 months ago
That's the only conclusion I can come to- I don't really see why else this wouldn't work.
samgordon
That's the only conclusion I can come to- I don't really see why else this wouldn't work.
2 months ago
I'm seeing the following in the console when I access the URL ((https://backboard.railway.com/graphql/v2) from the error message:
googletag/:212 Refused to load the script 'https://googleads.g.doubleclick.net/pagead/viewthroughconversion/17509959674/?random=1759161385975&cv=11&fst=1759161385975&bg=ffffff&guid=ON&async=1&en=gtag.config>m=45892e59n2v9228268922za204zd9228268922xec&gcd=13l3l3l3l1l1&dma=0&tag_exp=101509157~103116026~103200004~103233427~104527906~104528500~104684208~104684211~104948813~115480710&u_w=1512&u_h=982&url=https%3A%2F%2Fbackboard.railway.com%2Fgraphql%2Fv2&frm=0&tiba=Apollo%20Server&did=dYzg1YT&gdid=dYzg1YT&hn=www.googleadservices.com&npa=0&auid=696402301.1759155136&uaa=arm&uab=64&uafvl=Chromium%3B140.0.7339.210%7CNot%253DA%253FBrand%3B24.0.0.0%7CGoogle%2520Chrome%3B140.0.7339.210&uamb=0&uam=&uap=macOS&uapv=15.5.0&uaw=0&data=event%3Dgtag.config&rfmt=3&fmt=4' because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-1afec7c5979bc45c30422faa6a157902a4f215f733f19d5a65a8d7f346c11fd7' https://apollo-server-landing-page.cdn.apollographql.com https://embeddable-sandbox.cdn.apollographql.com https://embeddable-explorer.cdn.apollographql.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.