Fidelity - Error 16503/HTTP-403 (QMAC)

Aloke

Getting this today: "There was an unknown error trying to update this connection. Please try again later. (16503)"

Server msg: "HTTP-403 Error from Fidelity Investments Mac"

Type of connection: Direct connect FI (is it F-eye or F-el? font is the same).

Other institutions update fine. Are others seeing this? Known issue?

Thx.

Brad L Vandermoon

same thing for me this morning. this has been happening for about week now with vanguard as well.

Ploooplooo

Same 16503 error for first time this morning. This plus the ongoing one for Vanguard means the Quicken team are going to be especially busy!!!

Brad L Vandermoon

the quicken team may have a full backlog, but it does not appear as though they are addressing anything urgently.

ragush

Also same for me. Just started this morning. Using Quicken Mac.

Jeffrey Litvak

It is not possible to download transactions from Fidelity. Whenever I attempt to connected I get an error that reads "There was an unknown error trying to update this connection. Please try again later (16503)." Attempting to reconnect my Fidelity accounts results in the same error being displayed when I enter my Fidelity credentials into Quicken.

This problems seems to be somewhat different from what the Windows users are seeing but seems to be essentially the same issues — no connection to Fidelity.

Have others seen this problem? Is there a workaround?

Much thanks for any assistance.

NateSouthernCA

Same here. Just started this morning. Using Quicken Mac.

JMH

Same issue: There was an unknown error trying to update this connection. Please try again later. (16503)

Quicken Classic Premier Version 8.1.1 (Build 801.56891.100) on macOS 15.4

Quicken Anja

Hello All,

Thank you all for taking the time to bring this to our attention!

We will be forwarding this issue to the proper channels to have this further investigated. However, we request that you please navigate to Help > Report a problem within your Quicken program and submit a problem report with log files and screenshots attached in order to contribute to the investigation.

It would also aid the investigation to include a sanitized file when submitting the problem report. A sanitized file is a data file that removes personally identifiable information so you can comfortably share this file with the Quicken team.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

We apologize for any inconvenience in the meantime! Thank you.
(CBT-635)

Brad L Vandermoon

All of a sudden the fidelity connection is now working. It'd sure be nice if someone from quicken would tell us what was changed.

Quicken Kristina

Hello All,

We now have a Community Alert for this issue:

https://community.quicken.com/discussion/7961453/new-4-4-25-fidelity-investments-ol-295-16503-errors

Though we do not currently have an ETA, you can bookmark the Community alert linked above to get updates when available and to know when the issue is resolved. If you do not see the bookmark icon at the upper right, please make sure you are logged into the Community.

Thank you!

(Ticket #11694259/CTP-12631)

jacobs

@Brad L Vandermoon said: All of a sudden the fidelity connection is now working. It'd sure be nice if someone from quicken would tell us what was changed.

@Brad L Vandermoon Quicken may not even know. If the problem was caused by Fidelity blocking them temporarily, then Quicken notifies Intuit, who then tries to contact Fidelity. If it is indeed now fixed, the details of what happened and why may not have even made it back to Quicken. Or perhaps they do know, or perhaps it was a problem on Quicken's end — but Quicken doesn't often offer any information about what was wrong and who did what to fix it.

Brad L Vandermoon

@jacobs you must have missed the part about quicken sharing what they know about this.

jacobs

@Brad L Vandermoon said: you must have missed the part about quicken sharing what they know about this.

Nope. 😉 Re-read what I wrote:

(a) Quicken might not know what happened since multiple other parties can be involved.

(b) Whether they know or not, I have never seen Quicken offer a post-mortem explanation of what went wrong with any connectivity issue, so it's not going to be different in this case.