-
Notifications
You must be signed in to change notification settings - Fork 21
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
Document --no-browser still requires execution on same system as browser #55
Comments
The URL needs to be visited from the same system as the one running mozwire. I'm not sure why it would be polling anything though. (I'll try and have a look later) |
Ahh, thanks. I had it in my head that it would work like some other CLI login methods I've used, such as for example Azure CLI login, where the CLI provides a URL you authenticate via browser and the CLI keeps polling until successful, so the browser and CLI don't need to be on the same system. (Important when logging in remotely.) I ran mozwire from my laptop instead of the remote system and it works.
Sorry if I was ambiguous -- it's not polling, that's just how I expected it to work given my experience with other CLIs. It might be worth adding a note to the README saying that --no-browser doesn't support remote execution, and that you still need to run mozwire on the same host as the browser? Thanks! |
Updated the context of the issue to be a doc update in case there's some value to other users, but naturally please ignore/close if you feel my misunderstanding isn't likely to translate to other users And thanks for MozWire! I love that this lightweight tool exists for managing Mozilla's VPN. |
This caught me out as well. I had to generate the token on one machine and then copy it to the target. |
Running mozwire v0.8.1 on a remote system:
Then visiting this URL from my browser, I get a "Sign-in successful" response with the message "Please return to the Mozilla VPN app to complete setup." But mozwire never terminates.
In fact, strace shows it isn't polling a remote endpoint, so it's not really clear to me how this works or what the expected result is?
The text was updated successfully, but these errors were encountered: