I can sign in with Safari but not Chrome, even after trying:Clearing cookies and sessionEnabling third-party cookiesDisabling all extensionsIncognito windowAre there any known issues with the new community's sign-in system and Chrome?The sign in page just gets stuck like this:

Solved

Can't sign in to community in Chrome (Mac)

Forum|Forum|1 year ago
February 4, 2025
8 replies
392 views

I can sign in with Safari but not Chrome, even after trying:

Clearing cookies and session
Enabling third-party cookies
Disabling all extensions
Incognito window

Are there any known issues with the new community's sign-in system and Chrome?

The sign in page just gets stuck like this:

Experience

Best answer by 1P_Blake

Hey @Bikr 👋

Thanks for flagging this! We were definitely experiencing some login issues earlier, but we believe they’ve been resolved now. If you haven’t already, please try signing in again and let us know if you’re still running into trouble.

If anyone continues to have issues, feel free to share any error messages or details about what you’re seeing — we’re happy to look into it further!

Appreciate your patience, and thanks for being part of the Community!

K

kuoirad

Same here. Works fine in Firefox. I eventually got an "Unexpected Error" toast at the bottom of the page.

I haven't tried turning off uBlock or Privacy Badger yet, but they don't appear to be blocking anything of consequence that I can see.

Trying this in an Incognito window that doesn't have uBO or Privacy Badger enabled gives the same response, as does trying this in Chrome on Windows.

KG4ZOW

I had to try several times, using Firefox on macOS, before it would let me log in.

Rather irritating that we are required to run javascript from two different google hostnames in order to log in. Why does google need to know who's logging into this site? And why does 1Password feel it's okay to share this data with them?

Chromejob

The new community sign in page, and password reset, is flakey. My first attempt at required reset, no email for 10 mins. Second attempt, successful.

After the change, signing in has been intermittent (and I'm populating with, you guessed it, 1Password). Keep trying, is all I can suggest. Perhaps the new community servers are being DDoSed by all the loyal users coming back. 🤷

K

kuoirad

Worked on my Chromebook just now. I'll give it whirl again on my (work) Mac laptop later.

K

kuoirad

Had to clear cookies/cache again, but it's working on Chrome on my Mac and my Windows machines now.

BikrAuthor

I didn't change anything else on my end, but now I can sign in using Chrome on my Mac. 🙌

Hopefully, it was just a rollout glitch.

1P_BlakeAnswer

Community Manager

Hey @Bikr 👋

Thanks for flagging this! We were definitely experiencing some login issues earlier, but we believe they’ve been resolved now. If you haven’t already, please try signing in again and let us know if you’re still running into trouble.

If anyone continues to have issues, feel free to share any error messages or details about what you’re seeing — we’re happy to look into it further!

Appreciate your patience, and thanks for being part of the Community!

KG4ZOW

Now it's forcing me to allow javascript and hidden frames from `google.com` and `gstatic.com` (also google), PLUS javascript from `transcend-cdn.com` and `transcend.io` ... just to finish the login process. Once I'm logged in, I can block those things again and the site works just fine.

Seriously. Why is 1Password forcing their users to compromise their privacy in order to use the forum like this? Is there really that big a problem with spammers, scammers, or other undesirable types on the forum? Or are they getting some kind of kickback from google in exchange for being able to correlate our activities on this forum, with other web traffic where we've been forced to allow google to track us?

1P_SimonH

Community Manager

Hi @KG4ZOW,

I totally get why this would raise some eyebrows, and I appreciate you asking about it.

The reason you’re seeing those Google-related requests when logging in is because we use their reCAPTCHA service as part of the login process. reCAPTCHA looks at general traffic patterns to tell real people apart from automated attempts. It’s there to help keep bots and spam accounts out, not to track who’s signing in.

We also use a tool called Transcend that lets you customize your cookie preferences to meet your privacy needs.

I get that this kind of thing can feel a bit opaque, so I’ll pass along the feedback that more transparency here would be helpful.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded