-
Notifications
You must be signed in to change notification settings - Fork 140
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
authenticate the OAuth2 #373
Comments
Check that grive is running and listens on that port when you open the URL |
Thanks for your answer Vitalif. Yes grive is running: ss -lpn | grep grive But I'm not sure if I'm doing it correctly... I open the URL in other computer. Computer where grive is running is linux and I can't open the link (I think). And if I open the URL in other computer there's no point in trying to open localhost:xxxx, right? Regards |
You must open it on the same pc, it's how the new google auth flow works (they disabled the old one) - google redirects your browser to the local URL grive listens to. This URL contains the authentication code. Then grive has to do one more request to google with that code to get a token. You can copy the url that fails to open and request it with curl on the PC with grive |
Thank you very much!! you save my day. |
Hello,
When I visit the URL that comes up I receive an error:
It is not possible connect to localhost:42449.
I have used the app before with good results.
Thanks
The text was updated successfully, but these errors were encountered: