Chase HTTP Status 400 - Bad Request

ramrhein
ramrhein Member ✭✭✭
edited March 5 in Download, Add/Update Accounts (Windows)

I started getting an error that one of my chase accounts would not download. Trying to reset the account is giving a HTTP 400 error.

When will this be resolved. I can no longer connect any of the 12 chase bank and chase investment accounts.

Tagged:

Comments

  • Quicken Anja
    Quicken Anja Moderator mod

    Hello @ramrhein,

    Thanks for reaching out regarding this!

    This is a known issue that has been escalated internally, though we do not have an ETA on resolution at this time. While the investigation remains ongoing, please refer to this Community Alert for any and all available updates and information.

    We apologize for any inconvenience in the meantime! Thank you.

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

  • ramrhein
    ramrhein Member ✭✭✭

    Thank you Anja, I did see the Community Alert and I also noticed it is almost a Month old. I actually counted and I have 16 chase accounts and this will be a large issue if I cannot update any of them. I was hoping to maybe give a nudge to get this fixed since it may also be affecting the issues I read about BOA and this may be a larger issue than just BOA that is getting noticed. I tried restoring a backup before all of the accounts were disconnected but that didn't help as quicken is saying there is still a problem, and they need to be "fixed". So no joy with restoring from a backup.

  • ramrhein
    ramrhein Member ✭✭✭
    edited March 5

    Also today, I just started getting the same HTTP Status 400 - Bad Request error on my Fidelity HSA account.

    Update: It just worked when I changed the default browser to Chrome instead of Edge. Both browsers are fully up to date. Not sure why Edge caused a problem. I will try it for the Chase accounts.

  • ramrhein
    ramrhein Member ✭✭✭
    https://community.quicken.com/discussion/comment/20541515#Comment_20541515

    I was able to reauthorize the Chase accounts by changing the default browser to Chrome. I'm not sure why Microsoft Edge would always return the HTTP 400 error.

    Hopefully this additional information might be able to help the Quicken developers.

  • Quicken Anja
    Quicken Anja Moderator mod

    @ramrhein Thank you for following up and for sharing the additional details.

    I'm glad to hear you were able to successfully reauthorize your accounts by switching your default browser to Chrome. We appreciate you taking the time to post that workaround and the information about the HTTP 400 error occurring with Edge, as details like this can be helpful for our teams while the issue continues to be investigated.

    Thank you again for sharing your findings!

    -Quicken Anja
    Make sure to sign up for the email digest to see a round up of your top posts.

Categories