New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stripe cli login stuck on "Waiting for confirmation" #209
Comments
Hi @davefinarb, thanks for the report. Indeed, the Could you confirm the following?
|
Strangely both |
Weird! Thanks for closing the loop anyway. |
Same here, running Resets whatever it needed to. Before this, firefox opens, but it's just 'waiting' (no url in url bar) |
Hi @ob-stripe Made a quick video showing this behaviour https://www.youtube.com/watch?v=jrgS6uiPm1M&feature=youtu.be
|
Is there a way to print the browser URL instead, on systems that don't have a browser installed (I'm on WSL1 on Windows)? I know it's going to create a restricted key with certain permissions, so I'd like to use this method rather than creating my own restricted key that might have the wrong permissions. |
I'm having the same problem, running pop_os. Tried |
Any same solution for windows, running the command from Windows PowerShell is ending with the same error message. |
I started having a similar issue, using command prompt instead of powershell seemed to fix it. |
Too late to address the issue, but I was having the same issue. I tried running the stripe-cli using interactive mode, and provided the secret key, it worked.
and you are good to go!! Too late to address the issue, but this is how I fixed it! |
Issue
stripe login --api-key pk_test_****
it then shows
Your pairing code is: some-codes
This pairing code verifies your authentication with Stripe.
Press Enter to open the browser (^C to quit)
⣯ Waiting for confirmation...
Then it sticks in it and after some mins it shows
exceeded max attempts and quits
Expected Behavior
Probably opens a browser. Not sure.
Environment
Ubuntu 19 Linux
The text was updated successfully, but these errors were encountered: