Unable to access https://my.1password.com, tried multiple browsers, devices and networks

Options
asdfasdf12341234
asdfasdf12341234
Community Member
edited September 2023 in 1Password in the Browser

I'm unable to access the https://my.1password.com website. I keep getting a "Your connection is not private" page.

This is preventing me from signing up additional devices. My sign-in address in the 1Password app is "https://my.1password.com/". When I get to the "enter your password" step on the new device there's a really long loading state and then an error message is displayed, saying it is unable to sign in.

The 1Password apps runnings on my existing devices are all showing an "offline" icon that says it is unable to connect to the server:

This means that passwords aren't being synced between my different devices.

I've tried Chrome and Firefox on MacOS, Windows and Android devices. I've connected to two different home WiFi networks and a mobile data network. Same "Your connection is not private" message each time.

1Password Version: 8.10.16.
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • asdfasdf12341234
    asdfasdf12341234
    Community Member
    Options

    On my MacOS laptop I'm using 1Password for Mac 8.10.16.

  • asdfasdf12341234
    asdfasdf12341234
    Community Member
    Options

    For context I live in Auckland, New Zealand.

    Here's the output from nslookup:

    nslookup my.password.com

Server:     2404:4408:67ec:2200::1
Address:    2404:4408:67ec:2200::1#53

** server can't find my.password.com: NXDOMAIN

    Traceroute:

    traceroute: Warning: my.1password.com has multiple addresses; using 54.173.126.208
traceroute to my.1password.com (54.173.126.208), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  4.506 ms  3.981 ms  3.521 ms
 2  * * *
 3  * * *
 4  be1000.bdr01.akl05.akl.nz.vocus.network (175.45.102.233)  7.761 ms  6.010 ms  8.596 ms
 5  be100.bdr01.akl03.akl.nz.vocus.network (114.31.202.39)  147.787 ms
    be200.bdr03.lax01.ca.us.vocus.network (114.31.199.74)  128.983 ms  131.503 ms
 6  be100.bdr04.lax01.ca.us.vocus.network (114.31.199.37)  129.366 ms  130.705 ms
    be200.bdr04.lax01.ca.us.vocus.network (114.31.199.72)  131.250 ms
 7  eqix-da1.a100.1.com (206.223.118.150)  157.105 ms  157.219 ms  158.977 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *

    (its still going)

  • asdfasdf12341234
    asdfasdf12341234
    Community Member
    edited September 2023
    Options

    Output from nslookup:

    nslookup https://my.password.com

Server:     2404:4408:67ec:2200::1
Address:    2404:4408:67ec:2200::1#53

** server can't find https://my.password.com: NXDOMAIN

    Traceroute:

    traceroute my.1password.com
traceroute: Warning: my.1password.com has multiple addresses; using 54.173.126.208
traceroute to my.1password.com (54.173.126.208), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  4.506 ms  3.981 ms  3.521 ms
 2  * * *
 3  * * *
 4  be1000.bdr01.akl05.akl.nz.vocus.network (175.45.102.233)  7.761 ms  6.010 ms  8.596 ms
 5  be100.bdr01.akl03.akl.nz.vocus.network (114.31.202.39)  147.787 ms
    be200.bdr03.lax01.ca.us.vocus.network (114.31.199.74)  128.983 ms  131.503 ms
 6  be100.bdr04.lax01.ca.us.vocus.network (114.31.199.37)  129.366 ms  130.705 ms
    be200.bdr04.lax01.ca.us.vocus.network (114.31.199.72)  131.250 ms
 7  eqix-da1.a100.1.com (206.223.118.150)  157.105 ms  157.219 ms  158.977 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *

    (stopped it after 20 hops)

  • asdfasdf12341234
    asdfasdf12341234
    Community Member
    Options

    Reseting my router to factory defaults resolved the problem.

  • steph.giles
    steph.giles
    Options

    Hey @asdfasdf12341234,

    I'm sorry for the trouble, I'm glad you were able to get things back on track.

    Let us know if there's anything else we can help with and have a great weekend!

This discussion has been closed.