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; } } }

Bad request Error

debbeh

Hi,

Today, October 2, 2026, after signing in to update my accounts, Quicken prompted me to relink my Capital One and American Express accounts. Each attempt to reconnect fails with the following error:

A screenshot of the error is attached for reference.

Product: Quicken Classic for Mac, Version 9.2.2 (Build 902.61860.100)
macOS 27
Browser: Safari

Find more posts tagged with

Online Banking

Quicken Mac

Linking

Comments

debbeh

I found the solution,

It seems that Safari is having some issues connecting to Quicken servers. I have changed my default Browser to Google and it connected with no problems.

Egor Titov

I have been getting the same issues using Firefox. Can Quicken correct this? Is Chrome the only compatible browser?

Quicken Kristina

Hello @Egor Titov,

Thank you for reaching out! Typically, errors like this happen because a browser extension or setting is blocking communication. While Chrome usually works, it is not the only compatible browser.

Is your Firefox browser up to date? If you have any ad or pop-up blockers, please try pausing them. If you use an antivirus with a safe banking feature, please pause it, since it may pull banking sessions into its own custom browser. If you use a VPN, please try pausing it, since VPNs sometimes block communication between Quicken and the Financial Institution.

If the issue persists, please try temporarily setting an alternate browser as your default. Please do not use Brave or DuckDuckGo, since those browsers are known to not work with Quicken.

Please let me know how it goes!

Egor Titov

Thanks Kristina,

I'll check my settings in Firefox as you suggested and let you know. Just to let you know, I am on Catalina and cannot update it or Chrome anymore. I am trying to reconnect my Chase (Costco) credit card account, and the Chase website won't work with the Chrome version I have; however, my Firefox browser will open the Chase website but gets the HTTP Status 400 – Bad Request, as the OP displayed above, when trying to reconnect the account. This started a few days ago.

[Edited - Readability]

Quicken Kristina

Thank you for the additional information,

The older operating system may be partially causing the issue by limiting your ability to update Quicken and limiting which web browsers work, since Chrome and Edge no longer support Catalina.

If adjusting settings in Firefox doesn't help and you can't find a viable alternative browser to try, please let me know!

Thank you!

Egor Titov

Kristina, I have tried adjusting the settings in Firefox and still not able to get this account (Chase Costco) authorised. I don't use a VPN or antivirus. Firefox works okay until it gets to https://services.quicken.com and I receive HTTP Status 400 – Bad Request response. Seems like with my current OS my only viable browser is Firefox. I tried Safari, but my version is not accepted at the Chase website just like my version of Chrome.

debbeh

try those browsers might help.
Opera
DuckDuckGo

Egor Titov

Those two browsers will not install on my OS 10.15.8 Catalina. Thanks for the suggestions though.

Quicken Kristina

Thank you for your replies,

The HTTP 400 error may be caused by an old or corrupted cookie in the browser. You may want to go to your browser's Settings and clear the cache and cookies. WARNING: If you save your logins in your browser, what will likely happen is that you will need to manually re-enter those logins the next time you log into those online accounts.

I hope this helps!

smayer97

You do not have to clear ALL cookies, just the one associated with your website, e.g. Capital One or Chase, as applicable.

Egor Titov

Success! Clearing the cookies for quicken.com worked. Thank you everyone for your suggestions 😀

Quicken Kristina

Thank you for the follow-up,

I'm glad to hear that clearing your cookies fixed the issue!

If you need further assistance, please feel free to reach out!