Online Service with PNC leading me to: HTTP Status 400 – Bad Request

SamWilliamson

After a recent Quicken update, I lost connections to PNC. When I try to add an online service, I am asked to authorize Quicken, and I'm sent to what USUALLY is the bank login page. But now it is taking me to a page that says: HTTP Status 400 – Bad Request

this is the link: https://api.pnc.com/obp/login/web/authorize?client_id=retail_obp_hb_orchestrator_proxy_client_i00400

Help! I can't access my online services. (And Quicken seems to have shut down their online chatting or phone customer service.)

Quicken Anja

Hello @SamWilliamson,

Could you please provide a screenshot of what you are seeing? 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 given the option to add attachments.

Also, if you prefer to speak with Quicken Support, support is currently available for both phone and chat. You can access the phone number and chat support via this link.

Thank you!

Boatnmaniac

@SamWilliamson -

If this recently started, you could try restoring the backup file that Quicken created just before the software version update. Go to where your backup files are saved and look for the one that shows the version that was updated from in the file name. I will look something similar to this (shaded in yellow). That backup file should still have your PNC connection intact.:

And Quicken seems to have shut down their online chatting or phone customer service.

You need to allow popups on Quicken.com in order to access Chat and Phone support.

SRCDMC

It is June 28th and I am still getting the same problem. I've had it for about a week but today is the first time I received the HTTP Status 400 message. Is this a PNC issue?

Boatnmaniac

I have several PNC accounts in several different data files and am not receiving this error message so I doubt that it is a PNC issue.

Google "HTTP Status 400". There are somewhat different answers that come up depending on the browser that it being used but the one common thread in all of them is that it could be caused by a corrupted browser cache or a cookie(s) that is too large. Also, it seems that it is an issue on the client side (meaning on your system). So, I guess that is where I'd start.

Here are some of the steps that you can try that will hopefully resolve this issue. After each step, check to see if the issue is resolved. If it is not, move on to the next step. :

1. Clear Browser Cookies And Cache.
2. Reset Your Browser.
3. Restart Your Device and Other Hardware.
4. Flush DNS Cache.

Let us know whether or not this resolved the issue for you.