# CLI Login "Please log in with Google

**URL:** <https://community.doppler.com/t/cli-login-please-log-in-with-google/465>\
**Category:** Need Help\
**Created:** [December 25, 2021, 12:53am UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465 "2021-12-25T00:53:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bp4151](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/bp4151/32/318_2.png) [@bp4151](https://community.doppler.com/u/bp4151)\
**Post date:** [December 25, 2021, 12:53am UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/1 "2021-12-25T00:53:08Z")

</div>

I am trying to follow the instructions at [GitHub - DopplerHQ/python-doppler-env: Automatically inject Doppler secrets as environment variables for use during local development](https://github.com/dopplerhq/python-doppler-env). When I run  
doppler setup  
I am asked if I want to open the browser. I copy and paste the authorization code into the browser form, and then I am presented with a message “Please log in with Google”

I am thoroughly confused by this, so if anyone can possibly point me in the right direction, I’d really appreciate it.

Regards,  
Bruce

---

<div class="post-metadata">

**Author:** ![bp4151](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/bp4151/32/318_2.png) [@bp4151](https://community.doppler.com/u/bp4151)\
**Post date:** [December 26, 2021, 11:54am UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/2 "2021-12-26T11:54:58Z")

</div>

I figured it out. I think there was a difference in the web login interface between Chrome and Firefox on my machine. When I switched to Chrome, it worked fine. Not sure if that’s an issue with Firefox, or if it’s a plugin I am using within Firefox.

---

<div class="post-metadata">

**Author:** ![ryan-blunden](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ryan-blunden/32/9_2.png) [@ryan-blunden](https://community.doppler.com/u/ryan-blunden)\
**Post date:** [January 3, 2022, 3:21am UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/3 "2022-01-03T03:21:35Z")

</div>

Hi Bruce,

I wasn’t able to reproduce in Firefox 95.0.2 so I’m going to presume it’s related to an installed extension.

Thanks for reporting though!

---

<div class="post-metadata">

**Author:** ![mtmazurik](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/mtmazurik/32/327_2.png) [@mtmazurik](https://community.doppler.com/u/mtmazurik)\
**Post date:** [January 3, 2022, 9:42pm UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/4 "2022-01-03T21:42:13Z")

</div>

I am still getting “Please Login to Google” from a windows system, when I do a PS\> doppler login, and answer “Y” to use browser (I am using Chrome), I put in my Doppler account password: and I get a red error message “Please Login to Google”, weird. There is no area for account/username, simply password … and I did not set up with a Google integrated login on [Doppler.com](http://Doppler.com) I set up my account using my own corporate email and password. So why is “Log in to Google” coming up?

---

<div class="post-metadata">

**Author:** ![bp4151](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/bp4151/32/318_2.png) [@bp4151](https://community.doppler.com/u/bp4151)\
**Post date:** [January 3, 2022, 10:56pm UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/5 "2022-01-03T22:56:17Z")

</div>

Hi Ryan,

Thanks for the reply. I’ll try again with extensions off and report back.

Regards,  
Bruce

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [January 5, 2022, 4:06pm UTC](https://community.doppler.com/t/cli-login-please-log-in-with-google/465/6 "2022-01-05T16:06:32Z")

</div>

Hi all!

This was related to a bug in our re-auth flow that was discovered and fixed yesterday, so you shouldn’t be encountering this problem anymore! If you still are, let me know and I can take a look at what may be going on.

-Joel
