Can't login to https://my.1password.com or the app.

From one of my computers i can't login to https://my.1password.com from chrome.
I can't login from the windows app either.

Chrome says that NET::ERR_CERT_COMMON_NAME_INVALID

I can reach https://my.1password.eu but can´t login there.

I can login from my other computer.

I have extension 1.15.0 installed i chrome, but this one is not syncing with my account.

So nothing works on this computer.


1Password Version: 7.3.684
Extension Version: 1.15.0
OS Version: windows 10
Sync Type: Not Provided

Comments

  • bundtkatebundtkate

    Team Member

    Thanks for passing this along, @pettib! I've dropped our ops team a line just in case I'm wrong here, but given you're only seeing this on the one PC, it's probably a local issue resulting from some variety of third-party interference. Any security software on this PC that you don't use on the other? Maybe an anti-virus or firewall? Any extensions that could reasonably inspect your web traffic? Think safe browsing extensions. VPNs and proxies can also be a potential culprit. Let me know if you use any of the above on this PC and we'll take it from there. :+1:

  • I havs the same antivirus on both computers, webroot security. I think as you that this is a local problem but I can’t find it out. Both computers are on windows 10 in the same network. But I’m open for all tips how to solve this. I will try to see if I can find anything that is different.
    I think there is something weird about the communication with the server because of the problem with https.
    Is there any known malware that try to redirect communication with your servers ?

    /.Peter

  • bundtkatebundtkate

    Team Member

    Is it possible you've configured WebRoot to whitelist 1Password domains on one computer, but not the other, @pettib? What about updates – all browsers, WebRoot, and 1Password components fully up-to-date on both PCs? I'd suggest checking the logs in WebRoot regardless – just in case your settings are different. Plus, there's a possibility it has updated on this PC, thus changing its behavior, but not the other. All the same, if they've blocked something, they'll usually tell you. On the browser front, I suggest checking for updates manually, just in case. They're generally good about updating automatically, but they do need a kick in the butt.

    Finally, this can be a DNS issue. That's venturing a bit outside the area where I'm totally comfortable with my own knowledge, so I've asked our ops team what the best fix is if that's the trouble. If you find none of the above yields answers, let me know and I'll share how to deal with any DNS problems as soon as I hear back. :+1:

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file