• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs

Not what you are looking for? Ask the experts!

This forum thread needs a solution.

Server Error on Chrome Password Manager Extension

Spent over an hour with support earlier today and lost them on a remote system reboot.

I'm getting an error that says "System Error. We're working to resolve an issue that prevents us from completing your request. Try again later." when attempting to log into my password vault through the Chrome extension. No issues with Edge. I've removed and reinstalled Norton 360, removed and reinstalled the extension. Signed out of Google, then removed and reinstalled Chrome. No resolution. I'm only getting options for "Sign In" or "Help"; the extension isn't giving me an option to sign out and start over. Error started yesterday while I was attempting to update a new iPhone for mobile unlock.

Pretty frustrated tonight. There's clearly a corrupt setting somewhere, but lord only knows where or what or how to correct it!

Any ideas?


Kudos1 Stats

Re: Server Error on Chrome Password Manager Extension


Looks like the usual solution to corrupted extensions is to reset settings in Chrome. That worked. Bookmarks, etc., are still there, but looks like I've lost some other information. But nothing major.


Re: Server Error on Chrome Password Manager Extension

Reset Chrome settings to default

You can restore your browser settings in Chrome at any time. You might need to do this if apps or extensions you installed changed your settings without your knowledge. Your saved bookmarks and passwords won't be cleared or changed.

What changes when you restore your settings 

On your Chrome profile, the following settings will change to the default on all devices where you're signed in: 



Re: Server Error on Chrome Password Manager Extension


This is the challenge when dealing with a problem involving your browser and an add-on: Is there a problem with the add-on, or is it on the browser side. Of course, I'm paying Norton, so that's where I started. But if anything like that happens again, resetting to default appears to solve a world of ills!