Skip to main content

HTTP 400 During OAUTH or Signing into Quicken on a Web Browser

HTTP 400, Bad Request

A
Written by Anthony

When a user gets an HTTP 400 error, this issue is often an issue with the web browser or website itself, not Quicken or Simplifi. However, this issue can often be resolved by doing the following.
Below are the two things we can do to attempt to resolve this issue.

Instructions

- Guide the user to navigate to their default browser and clearing the cookies and cache. If the customer expresses concerns about data-loss, reassure them it is completely safe and all it will do is sign them out of websites and reset temporary site preferences, but all they have to do is sign back in and they will not lose any data.

  • Give tailored instructions based off the browser they are using.

If that fails, you can have them change their default browser temporarily and then try to do the action that gave them the bad request once more and see if that worked.

macOS Ventura, Sonoma, Sequoia, and Later

  • Install your new web browser.

  • Click the Apple menu () in the corner of your screen.

  • Choose System Settings.

  • Click Desktop & Dock in the sidebar.

  • Scroll down on the right side.

  • Choose a web browser from the Default web browser menu.

Windows

  1. Open Settings.

  2. Click Apps on the left menu.

  3. Select Default apps.

  4. Type your preferred browser name (like Chrome or Firefox) in the search box under Set defaults for applications.

  5. Click on your preferred browser from the results.

  6. Click the Set default button at the top

After they try either clearing cache and cookies or changing their default web browser, ask the user to try again. If it still fails, escalate.




Did this answer your question?