1Password X: error when saving: "We were unable to reach the server"

fryrpc · July 2018

I have this issue quite frequently - I use 1PasswordX in the Firefox Browser running on a Linux PC. I sign into 1PasswordX and when I press the CTRL + . shortcut I get my vault with logins accessible. I sign into a website and go to change my password, or just visit a page that has a password field, and either generate a new password, or put one in on the web page manually - I am prompted to save in 1Password - Great - but when I select to do that I get the error - "We were unable to reach the server. Please check your internet connection and try again."

I think this is somehow related to the fact that when I login to 1PasswordX I am automatically taken to the 1Password web login page in a new tab - sometimes I login and sometimes I don't - either way 1PasswordX appears to work. Even when I do login after 10 minutes it logs me out of that webpage anyway - I think if I try and save a password within the 10 minute window it might work.

1Password Version: Not Provided
Extension Version: 1.8.2
OS Version: Linux Mint
Sync Type: 1Password Team Subscription

AGAlumB · July 2018

@fryrpc: Thanks for reaching out. I’m sorry for the trouble! To get a better sense of what might be causing that for you, please grab the logs the next time this happens:

Open Firefox and go to about:debugging#addons
Select "Enable add-on debugging"
Click "Debug" underneath "1Password X - Password Manager"
With the console open, open the blank page again by clicking the 1Password icon in the toolbar
Screenshot or copy/paste the logs that appear in the console

Also, if you create a new profile, do you experience the same issue there? Thanks in advance!

fryrpc · August 2018

🚩 ap background.js:1:912803
🏁 ap background.js:1:912803
🚩 sl background.js:1:912803
🏁 sl background.js:1:912803
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected while context is inactive: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected while context is inactive: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
[Show/hide message details.] Promise rejected while context is inactive: Promised response from onMessage listener went out of scope
s.js:1
[Show/hide message details.] Promise rejected while context is inactive: Promised response from onMessage listener went out of scope
ExtensionContent.jsm:493
Error: Promised response from onMessage listener went out of scope background.js:1:1339617
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
inline.js:1
Error: Promised response from onMessage listener went out of scope background.js:1:1339617
Failed to save login: TypeError: "this.syncer is undefined"
runSyncermoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1364883sMmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1378169responsemoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1399229rmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1339821 background.js:1:912803
Error: Promised response from onMessage listener went out of scope background.js:1:1339617
Failed to save login: TypeError: "this.syncer is undefined"
runSyncermoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1364883sMmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1378169responsemoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1399229rmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1339821 background.js:1:912803
Failed to save login: TypeError: "this.syncer is undefined"
runSyncermoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1364883sMmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1378169responsemoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1399229rmoz-extension://61d39510-6c62-4f4c-8290-517e5bc81bd6/background/background.js:1:1339821 background.js:1:912803

fryrpc · August 2018

dteare · August 2018

Thank you for the details, @fryrpc! It was very helpful.

We've been tracking this issue for a while now and believe we have it fixed in the beta. If you're game, please install the 1Password X beta and with any luck you'll be all set.

If you'd like to stay on the official channel, you should be able to avoid this bug by keeping your Autolock timeout at 20 minutes or less.

I hope that helps. Please let me know how it turns out.

++dave;

fatso83 · August 2018

I am getting the same error message on ArsTechnica's sign up page, but my debug logs are not the same. Wondering if I should start a new thread or if it's sufficient to post things here? This behaviour has been there at least since June. Currently running 1.10.1 on Firefox. Haven't tried the beta fix (yet), I must attest, though the comment seems to imply it might be relevant, as I currently disabled the Autolock feature.

Regardless, here are some of my logs, along with the request results (not posting the actual requests, since they contain session ids and such).

Console logs

🚩 ap background.js:formatted:57486
🏁 ap background.js:formatted:57486
Invalid chrome URI: /
🚩 gp background.js:formatted:57486
🏁 gp background.js:formatted:57486
Error: Promised response from onMessage listener went out of scope
background.js:formatted:78823
🚩 sl background.js:formatted:57486
🏁 sl background.js:formatted:57486
🚩 fgp start background.js:formatted:57486
🏁 fgp end background.js:formatted:57486
[Show/hide message details.] Promise rejected after context unloaded: n is null
ExtensionContent.jsm:493
Error: n is null
background.js
🚩 ap background.js:formatted:57486
🏁 ap background.js:formatted:57486
🚩 ap background.js:formatted:57486
🏁 ap background.js:formatted:57486
🚩 sl background.js:formatted:57486
🏁 sl background.js:formatted:57486
Error: n is null background.js
[_request] Request "/api/v2/vault/mj56pss5lzwontdscgd4r4wgca/4/items" failed: ServerError: "Authentication required."
tmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1030989_handleQwestErrormoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1228249fmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1442197umoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1441884mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583330mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583268smoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1582803 background.js:formatted:57486
🚩 gp background.js:formatted:57486
🏁 gp background.js:formatted:57486
[Show/hide message details.] Promise resolved after context unloaded
inline.js:1
[_request] Request "/api/v2/vault/mj56pss5lzwontdscgd4r4wgca/4/items" failed: ServerError: "Authentication required."
tmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1030989_handleQwestErrormoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1228249fmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1442197umoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1441884mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583330mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583268smoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1582803 background.js:formatted:57486
Error: background.js:formatted:61880
LoginRecipes: getRecipes: falling back to a synchronous message for: moz-extension://0aa94036-75f2-4514-a43d-26a779c90560 LoginRecipes.jsm:243
[_request] Request "/api/v2/vault/osnxuffyoxpcnx74rl7humpipu/284/items" failed: ServerError: "Authentication required."
tmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1030989_handleQwestErrormoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1228249fmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1442197umoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1441884mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583330mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583268smoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1582803 background.js:formatted:57486
[_request] Request "/api/v2/vault/osnxuffyoxpcnx74rl7humpipu/284/items" failed: ServerError: "Authentication required."
tmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1030989_handleQwestErrormoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1228249fmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1442197umoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1441884mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583330mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583268smoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1582803 background.js:formatted:57486
Failed to save login: ServerError: "Authentication required."
tmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1030989_handleQwestErrormoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1228249fmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1442197umoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1441884mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583330mmoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1583268smoz-extension://0aa94036-75f2-4514-a43d-26a779c90560/background/background.js:1:1582803 background.js:formatted:57486
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
inline.js:1
Error: Promised response from onMessage listener went out of scope background.js:formatted:78823
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
inline.js:1
Error: Promised response from onMessage listener went out of scope
background.js:formatted:78823
[Show/hide message details.] Promise rejected after context unloaded: Promised response from onMessage listener went out of scope
inline.js:1

Request details

https://kopseng-co.1password.com/api/v2/vault/osnxuffyoxpcnx74rl7humpipu/284/items
{"errorCode":102,"errorMessage":"Authentication required.","requestId":11454022}
PATCH 
HTTP 401

https://kopseng-co.1password.com/api/v2/vault/mj56pss5lzwontdscgd4r4wgca/4/items
{"errorCode":102,"errorMessage":"Authentication required.","requestId":11453553}

https://kopseng-co.1password.com/api/v2/vault/mj56pss5lzwontdscgd4r4wgca/4/items
{"errorCode":102,"errorMessage":"Authentication required.","requestId":20860142}

https://kopseng-co.1password.com/api/v2/vault/osnxuffyoxpcnx74rl7humpipu/284/items
{"errorCode":102,"errorMessage":"Authentication required.","requestId":20860562}



The plugin was not locked and I manually also ensured I was logged into the vault in another tab.

AGAlumB · August 2018

@fatso83: Thank you for sharing those details! I believe we've found a solution to this, and hopefully we'll have an update for everyone before long. :)

TomD · October 2018

I am having the same issue with Firefox 62.0.3. Here is the console log:

Could not map contract ID '@mozilla.org/fxaccounts/push;1' to CID {1b7db999-2ecd-4abf-bb95-a726896798ca} because no implementation of the CID is registered. components.manifest:163
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. Grammarly.html
Content Security Policy: The page’s settings blocked the loading of a resource at self (“default-src”). Source: call to eval() or related function blocked by CSP. background.js:1
crypto tests: 342ms background.js:1:1179037
[Show/hide message details.] Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist.
webrequest.js:111
Error: An unexpected error occurred
undefined
🚩 ap background.js:1:952258
🏁 ap background.js:1:952258
PBES2g-HS256(100000): 184ms background.js:1:1047402
[LM] @startMonitoring (autolock=10) background.js:1:1410224
PBES2g-HS256(100000): 180ms background.js:1:1047402
🚩 ap background.js:1:952258
🏁 ap background.js:1:952258
[snip
[_request] Request "/api/v1/account?attrs=me,user-flags,account-flags,billing,tier" failed: ClientError: "Request timed out. This probably means that you’re not connected to the Internet or our servers are down."
tmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1031210_handleQwestErrormoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1227794fmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442436umoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442123mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583569mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583507smoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583042 background.js:1:952258
[action/account#getAccountWithAttrs] ClientError: "Request timed out. This probably means that you’re not connected to the Internet or our servers are down."
tmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1031210_handleQwestErrormoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1227794fmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442436umoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442123mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583569mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583507smoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583042 background.js:1:952258
[action/auth#handleSignInSuccess] ClientError: "Request timed out. This probably means that you’re not connected to the Internet or our servers are down."
tmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1031210_handleQwestErrormoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1227794fmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442436umoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442123mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583569mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583507smoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583042 background.js:1:952258
[action/auth#signInWithEmailAndPassword] ClientError: "Request timed out. This probably means that you’re not connected to the Internet or our servers are down."
tmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1031210_handleQwestErrormoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1227794fmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442436umoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442123mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583569mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583507smoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583042 background.js:1:952258
Unknown reason code 105 ClientError: "Request timed out. This probably means that you’re not connected to the Internet or our servers are down."
tmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1031210_handleQwestErrormoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1227794fmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442436umoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1442123mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583569mmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583507smoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1583042 background.js:1:952258
🚩 ap background.js:1:952258
🏁 ap background.js:1:952258

[snip]

Unable to save item, running syncer and retrying... background.js:1:1404875
Failed to save login: TypeError: "this.syncer is undefined"
runSyncermoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1404332saveItemmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1404949 background.js:1:952258
Unable to save item, running syncer and retrying... background.js:1:1404875
Failed to save login: TypeError: "this.syncer is undefined"
runSyncermoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1404332saveItemmoz-extension://69c51324-d3b3-c84f-8fd6-9cdee3377bf8/background/background.js:1:1404949 background.js:1:952258

[snip]

🚩 ap background.js:1:952258
🏁 ap background.js:1:952258

[snip]

Use of nsIFile in content process is deprecated.

AGAlumB · October 2018

@TomD: Please update to 1.11.0, which was released a few hours ago. Are you still encountering the same issue?

TomD · October 2018

seems to be good to go. thanks!

AGAlumB · October 2018

Excellent! Thanks for the update. You are most welcome! I'm glad to hear that resolved it for you. It sounds like you should be all set, but don't hesitate to reach out if we can be of further assistance. Cheers! :)

brucebc · October 2018

Hi! I am using 1PW X 1.11.0 Chrome, and this still happens when I try to save a new password from a form fill on a web site. I'm guessing it's related to the fact that extension and form fills and logged in vault page are not sync'd? When I get this message, I check the extension: it's signed in. When I open the vault page via the extension, I get the login screen. Which the extension then offers to fill! (seems not right). Then after I log in and open the vault page, and then go back to the form fill page, I can save the new password without error.

Also if you think it's related to sync state across the various pages, extensions, etc.: I notice I can set a logout delay of 999 minutes on 1PW X Account Security page; but on Profile page can only set browser auto-lock delay to 300min. How are the two settings different? And could these types of differences affect the error we're discussing?

beyer · October 2018

@brucebc: Nope, that doesn't seem right at all! You shouldn't need to do this, but can you please try removing your account from the settings page and adding it back again?

If you still see an issue after doing that, I'd love to troubleshoot this issue further with you. To do so, please follow this link using your browser with 1Password X installed. When you reach the contact form, please include the link to this thread.

Please let us know how it goes. ❤️

-Beyer

brucebc · October 2018

Hi beyer:

Belated update: your suggestion did fix this issue (removing and re-adding account).

Thanks!

Bruce

AGAlumB · October 2018

Glad that did the trick! Thanks for the update. It sounds like you should be in good shape, but we're here if you need us. :)

masondon · November 2018

I am seeing this same issue, using both Windows 10 and Max OS and both Firefox and Chrome. I'm using 1.12.3 on all browsers. Trying to save a new login, I am getting that error

dankyung · November 2018

Hi @masondon,

To better understand what is going on, please provide us with the logs:

On Firefox:

Open Firefox and go to about:debugging#addons
Select "Enable add-on debugging"
Click "Debug" underneath "1Password X - Password Manager"
Save a new login to trigger the error
Screenshot or copy/paste the logs that appear in the console

On Chrome:

Open Chrome and go to chrome://extensions/
Select "Developer mode" to toggle it on
Under 1Password X, click "background page"
Select the "Console" tab
Save a new login to trigger the error
Copy everything in the Console and save it to a text file

masondon · November 2018

From my Windows 10 Firefox......

Could not map contract ID '@mozilla.org/fxaccounts/push;1' to CID {1b7db999-2ecd-4abf-bb95-a726896798ca} because no implementation of the CID is registered. components.manifest:167
Error: Could not establish connection. Receiving end does not exist. h0-main.js:1:27142
crypto tests: timer startedbackground.js:9
crypto tests: 35msbackground.js:9
Error: Could not establish connection. Receiving end does not exist. h0-main.js:1:27142
PBES2g-HS256(100000): timer startedbackground.js:9
PBES2g-HS256(100000): 166msbackground.js:9
[LM] @startMonitoring (autolock=10) background.js:31:198356
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:16
[action/Session#verify] ClientError: Please authenticate with MFA
Stack trace:
t@moz-extension://9ffc280d-8cf6-4de2-a5a6-14c84476db9f/background/background.js:9:423109
e/this.verify/</<@moz-extension://9ffc280d-8cf6-4de2-a5a6-14c84476db9f/background/background.js:9:460499
background.js:9:242228
[action/auth#signInWithEmailAndPassword] ClientError: Please authenticate with MFA
Stack trace:
t@moz-extension://9ffc280d-8cf6-4de2-a5a6-14c84476db9f/background/background.js:9:423109
e/this.verify/</<@moz-extension://9ffc280d-8cf6-4de2-a5a6-14c84476db9f/background/background.js:9:460499
background.js:9:242228
Error: background.js:9:423109
Unable to save item, running syncer and retrying... background.js:31:193476
No syncer available. Skipping runSyncer for SNVPEVV5FRCDJOWK55MXJKCP4E. background.js:31:192896
Failed to save login: TypeError: this.client is undefined
Stack trace:
C/this.saveItem@moz-extension://9ffc280d-8cf6-4de2-a5a6-14c84476db9f/background/background.js:31:193611
background.js:31:234253
error occurred while processing 'sources: TypeError: can't access dead object
Stack: createNonSourceMappedActor@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/utils/TabSources.js:312:1
createSourceActors/<@resource://devtools/shared/base-loader.js -> resource://devtools/server/actors/utils/TabSources.js:400:19
Line: 312, column: 1 main.js:1624

From my Mac Firefox........

Could not map contract ID '@mozilla.org/fxaccounts/push;1' to CID {1b7db999-2ecd-4abf-bb95-a726896798ca} because no implementation of the CID is registered. components.manifest:160
crypto tests: 22ms background.js:9:320215
PBES2g-HS256(100000): 152ms background.js:9:347373
[model/symmetric_key#decrypt] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[model/symmetric_key#decryptWithKey] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[model/keyset#decryptWithKey] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#decryptKeysetFindParent] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#getDecryptedKeyset] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#decryptKeysets] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[_request] Request "/api/v2/auth/verify" failed: ServerError: "Authentication required."
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:422875
_handleQwestError moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:456898
f moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:594126
u moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:593817
p moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452876
p moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452814
s moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452349
background.js:9:455821
[action/Session#verify] ClientError: "Invalid email or password"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460723
background.js:9:242228
[action/auth#signInWithEmailAndPassword] ClientError: "Invalid email or password"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460723
background.js:9:242228
PBES2g-HS256(100000): 148ms background.js:9:347373
[model/symmetric_key#decrypt] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[model/symmetric_key#decryptWithKey] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[model/keyset#decryptWithKey] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#decryptKeysetFindParent] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#getDecryptedKeyset] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[action/keyset#decryptKeysets] DOMException: "The operation failed for an operation-specific reason" background.js:9:242228
[_request] Request "/api/v2/auth/verify" failed: ServerError: "Authentication required."
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:422875
_handleQwestError moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:456898
f moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:594126
u moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:593817
p moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452876
p moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452814
s moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:24:452349
background.js:9:455821
[action/Session#verify] ClientError: "Invalid email or password"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460723
background.js:9:242228
[action/auth#signInWithEmailAndPassword] ClientError: "Invalid email or password"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460723
background.js:9:242228
PBES2g-HS256(100000): 146ms background.js:9:347373
[LM] @startMonitoring (autolock=10) background.js:31:198356
Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:16
Unchecked lastError value: Error: Promised response from onMessage listener went out of scope popup.js:31
componentDidMount
moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/popup/popup.js:31:193872
[action/Session#verify] ClientError: "Please authenticate with MFA"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460499
background.js:9:242228
Error: background.js:9:423109
[action/auth#signInWithEmailAndPassword] ClientError: "Please authenticate with MFA"
t moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:423109
verify moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:9:460499
background.js:9:242228
Use of nsIFile in content process is deprecated. NetUtil.jsm:266:12
Unable to save item, running syncer and retrying... background.js:31:193476
No syncer available. Skipping runSyncer for SNVPEVV5FRCDJOWK55MXJKCP4E. background.js:31:192896
Failed to save login: TypeError: "this.client is undefined"
saveItem moz-extension://902b3670-b9c6-4240-ab20-5bfdf627ba80/background/background.js:31:193611
background.js:31:234253

masondon · November 2018

From my Windows 10 Chrome......

background.js:9 [action/Session#verify] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
background.js:9 [action/auth#signInWithEmailAndPassword] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
background.js:9 Uncaught (in promise) Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
background.js:31 Unable to save item, running syncer and retrying...
background.js:31 No syncer available. Skipping runSyncer for SNVPEVV5FRCDJOWK55MXJKCP4E.
C.runSyncer @ background.js:31
C.saveItem @ background.js:31
async function (async)
C.saveItem @ background.js:31
je @ background.js:31
save-login-response @ background.js:31
i @ background.js:16
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
messageListener @ extensions::messaging:240
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnMessage @ extensions::messaging:392
background.js:31 Failed to save login: TypeError: Cannot read property 'saveItem' of undefined
at C.saveItem (background.js:31)
save-login-response @ background.js:31
async function (async)
save-login-response @ background.js:31
i @ background.js:16
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
messageListener @ extensions::messaging:240
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnMessage @ extensions::messaging:392

From Mac Chrome......

background.js:9 [action/Session#verify] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
background.js:9 [action/auth#signInWithEmailAndPassword] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
background.js:9 Uncaught (in promise) Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
background.js:31 [LM] @didUserGoInactive: Last activity detected: 10 minutes ago
background.js:31 [LM] Posting lock notifcation
background.js:31 [LM] @stopMonitoring
background.js:31 [LM] Locked at Wed Nov 14 2018 11:59:24 GMT-0600 (Central Standard Time)
background.js:9 PBES2g-HS256(100000): 48.23291015625ms
background.js:31 [LM] @startMonitoring (autolock=10)
background.js:9 [action/Session#verify] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
g @ background.js:9
Promise.catch (async)
(anonymous) @ background.js:9
verify @ background.js:9
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
signin @ background.js:9
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
Uy @ background.js:9
(anonymous) @ background.js:31
async function (async)
(anonymous) @ background.js:31
Promise @ background.js:31
g @ background.js:31
C.startSync @ background.js:31
async function (async)
C.startSync @ background.js:31
r.length.ye.then @ background.js:31
Promise.then (async)
pe @ background.js:31
async function (async)
pe @ background.js:31
getBackground.n @ popup/popup.js:31
chrome.runtime.getBackgroundPage.t @ popup/popup.js:31
(anonymous) @ extensions::runtime:110
safeCallbackApply @ extensions::uncaught_exception_handler:27
handleResponse @ extensions::sendRequest:52
background.js:9 [action/auth#signInWithEmailAndPassword] Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
(anonymous) @ background.js:9
g @ background.js:9
Promise.catch (async)
(anonymous) @ background.js:9
Uy @ background.js:9
(anonymous) @ background.js:31
async function (async)
(anonymous) @ background.js:31
Promise @ background.js:31
g @ background.js:31
C.startSync @ background.js:31
async function (async)
C.startSync @ background.js:31
r.length.ye.then @ background.js:31
Promise.then (async)
pe @ background.js:31
async function (async)
pe @ background.js:31
getBackground.n @ popup/popup.js:31
chrome.runtime.getBackgroundPage.t @ popup/popup.js:31
(anonymous) @ extensions::runtime:110
safeCallbackApply @ extensions::uncaught_exception_handler:27
handleResponse @ extensions::sendRequest:52
background.js:9 Uncaught (in promise) Error: Please authenticate with MFA
at new t (background.js:9)
at background.js:9
t @ background.js:9
(anonymous) @ background.js:9
postMessage (async)
r @ background.js:24
l.setImmediate @ background.js:24
i @ background.js:24
u @ background.js:24
n @ background.js:24
(anonymous) @ background.js:24
Promise.then (async)
n @ background.js:24
f @ background.js:24
(anonymous) @ background.js:24
(anonymous) @ background.js:24
p @ background.js:24
s @ background.js:24
postMessage (async)
r @ background.js:24
l.setImmediate @ background.js:24
i @ background.js:24
u @ background.js:24
(anonymous) @ background.js:24
f @ background.js:24
(anonymous) @ background.js:24
(anonymous) @ background.js:24
p @ background.js:24
s @ background.js:24
postMessage (async)
r @ background.js:24
l.setImmediate @ background.js:24
i @ background.js:24
u @ background.js:24
E @ background.js:24
load (async)
i.send @ background.js:24
(anonymous) @ background.js:24
(anonymous) @ background.js:24
m.map @ background.js:24
map @ background.js:24
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
request @ background.js:9
post @ background.js:9
lc @ background.js:9
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
verify @ background.js:9
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
signin @ background.js:9
(anonymous) @ background.js:9
Promise.then (async)
(anonymous) @ background.js:9
Uy @ background.js:9
(anonymous) @ background.js:31
async function (async)
(anonymous) @ background.js:31
Promise @ background.js:31
g @ background.js:31
C.startSync @ background.js:31
async function (async)
C.startSync @ background.js:31
r.length.ye.then @ background.js:31
pe @ background.js:31
Promise.then (async)
async function (async)
pe @ background.js:31
getBackground.n @ popup/popup.js:31
chrome.runtime.getBackgroundPage.t @ popup/popup.js:31
(anonymous) @ extensions::runtime:110
safeCallbackApply @ extensions::uncaught_exception_handler:27
handleResponse @ extensions::sendRequest:52
background.js:31 Unable to save item, running syncer and retrying...
background.js:31 No syncer available. Skipping runSyncer for SNVPEVV5FRCDJOWK55MXJKCP4E.
C.runSyncer @ background.js:31
C.saveItem @ background.js:31
async function (async)
C.saveItem @ background.js:31
je @ background.js:31
save-login-response @ background.js:31
i @ background.js:16
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
messageListener @ extensions::messaging:240
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch_ @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnMessage @ extensions::messaging:392
background.js:31 Failed to save login: TypeError: Cannot read property 'saveItem' of undefined
at C.saveItem (background.js:31)

masondon · November 2018

Thanks for the replt, Dan. I didn't notice you wanted the Chrome one in a text file. Let me know if any of this is helpful......sorry, had to wait to post this one, was posting too fast :)

dankyung · November 2018

@masondon,

You shouldn't have to do this, but removing your account from the settings page and adding it back again should resolve this problem.

If not, I'd like to troubleshoot this issue further with you. Sorry for any trouble this may have caused you.

Dan

masondon · November 2018

That did the trick! Did in both browsers on both machines, was able to add a new entry in all 4 instances. Thanks for the help!

dankyung · November 2018

@masondon, glad to help! :)

1Password X: error when saving: "We were unable to reach the server"

Comments