Chase HTTP Status 400 - Bad Request
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.
Comments
-
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.0 -
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.
0 -
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.
0
Categories
- All Categories
- 47 Product Ideas
- 34 Announcements
- 244 Alerts, Online Banking & Known Product Issues
- 22 Product Alerts
- 513 Welcome to the Community!
- 679 Before you Buy
- 1.4K Product Ideas
- 55.5K Quicken Classic for Windows
- 16.8K Quicken Classic for Mac
- 1K Quicken Mobile
- 829 Quicken on the Web
- 124 Quicken LifeHub
