nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

4 different logins to Fidelity, now 1 stops working...rejects password.

Mark Stevens

Hi - longtime quicken user and have 15 plus accounts under 4 user ids connected to Fidelity. All has worked great for years. Now, my main account does not connect. It keeps telling me my password is wrong (which it is not). It locked my out of my Fidelity account. However, the password is correct. I can log in via the Fidelity website fine. I do use 2FA at Fidelity, but never an issue with Quicken. This was all caused once I tried to add a new fidelity account to Quicken. I heard there was some new method coming for connection, but why is it breaking the old??? I need these to connect. Any ideas?

Find more posts tagged with

Online Banking

Mac

Comments

Quicken Anja

Hello @Mark Stevens,

We appreciate you reaching out!

Could you please provide a screenshot of the error you receive? If needed, please refer to this Community FAQ for instructions on how to attach a screenshot. Alternatively, you can also drag and drop screenshots to your response if you are not give the option to add attachments.

Thank you!

Mark Stevens

fidelity-quicken-error.pdf

Attached but there is no real error message. It will connect for three of the accounts, but not the fourth. The fourth is the one I am attempting to add a new account. It says the password is incorrect. However, it cannot be. I have verified it 5 times on both the website and in my other program. Fidelity is blocking this one account from connecting. The others work great. Thanks for responding.

Mark Stevens

please close this issue. The problem appears to be in the vault. The vault had an old password. Even if I entered the new password in all the fields, it would still fail. Once I went into the vault and reset it, it connected.

Quicken Anja

@Mark Stevens Thanks for the update, and we appreciate you sharing the solution!

We'll go ahead and close this post as requested. If you run into anything else, feel free to reach out again.

Thank you!