Browser: "Errors have occurred" when creating new Chrome extension login

[minmarble]

When attempting to make a new login for a site using the Chrome browser extension, this error pops up:

You're able to make a login using the web vault, but it doesn't seem to sync with the extension itself and will not show the new login you've made in the extension.

I have disabled all other Chrome extensions except Bitwarden itself to test for conflicts and it still seems to be a problem.

[kspearrin]

@minmarble It appears that you are having issues connecting to the bitwarden server for some reason. Can you try doing a manual sync and see if you get an error with that as well?

[minmarble]

@kspearrin After adding a login to the web vault, then going to Settings > Manage section > Sync in the extension, it still does not seem to update, even after the "Syncing complete" prompt.

It also doesn't seem to update to the latest time of the sync when it's done manually... it says the last sync was done more than 30 minutes ago, which is when I opened Chrome (and started my computer) for the first time today.

[kspearrin]

@minmarble Are you familiar with how to view the dev tools on the extension to see if there are any network errors occurring during the sync?

You can swing into our dev chat room if you like and I can walk you through it: https://gitter.im/bitwarden/Lobby

[jjdelc]

Seeing same error here (Firefox Nightly + Ubuntu), the text is a bit different. It says "An unexpected error has occurred" when trying to manually add a new site.

[kspearrin]

@jjdelc log out and back in app to fix it for now.

[jjdelc]

Logged out, now I see the same red error trying to log in.

[kspearrin]

Can you email me at https://bitwarden.com/contact so I can get more info.

[jjdelc]

Done, I also joined the gitter channel

[jjdelc]

@minmarble do you have uMatrix installed? I just tried disabling the extension completly and it worked.

The problem was that even when I "switched off" the filtering, I still had trouble. And there were no sources pointing to anything bitwarden in the uMatrix menu to indicate that some requests were being blocked. The only way to get around was completly disable the extension.

[Primokorn]

@jjdelc no need to disable uMatrix. There are a few connections to allow in the _behind-the-scene_ mode. Here is what I allowed on my end:

behind-the-scene api.bitwarden.com xhr allow
behind-the-scene identity.bitwarden.com xhr allow
behind-the-scene maillink.bitwarden.com other allow
behind-the-scene vault.bitwarden.com other allow

[jjdelc]

@Primokorn Thanks! I was trying with matrix-off and didn't have any luck.

I found though that disabling and enabling it also resolved the issue, a re-enabled uMatrix even without any rules added also allowed bitwarden to work.

[LivingWithHippos]

I fixed this with the rule "* bitwarden.com * allow" into the my-rules section

[Primokorn]

@jjdelc Disabling uMatrix is not a good idea since you allow (even temporarily) all the traffic.
@LivingWithHippos yes... if you want to allow everything from bitwarden including analytics.

[bb010g]

For whatever reason, when I checked the log and tried to enable it from there, it was marked as coming from youtube.com despite trying to create the password in a different tab. I ended up using @Primokorn's exceptions with a * filter instead of behind-the-scene.

[SylwesterZarebski]

With Firefox 54.0.1 behind-the-scene do not work for me. I have to use * instead, like @bb010g do.

[kspearrin]

This should be resolved now.