In microsoft.public.money, sherman wrote:

- quote -

This is from the OFX spec:

:Note: The server must return a code in the 400s for any problem that prevents it from
rocessing the request file. Processing problems include failures relating to security,
:communication, parsing, or the Open Financial Exchange declaration (for example, the client
:requested an unsupported language). For content errors such as wrong USERPASS or invalid
:account, the server must return a valid Open Financial Exchange response along with code 200.
:If a communication time-out error occurs while an OFX server and a back-end server are
:communicating to fill a request, then the server MUST return a code in the 500s.

If I go to https://ofx412.fidelity.com I get a note that the
certificate does not match the URL. If I go to
https://ofx.fidelity.com, I get no response. When I do an update it
actually goes to ofx412.fidelity.com as shown by netstat, and it
succeeds.

So has this problem for you been going on long?

- quote -

I have this same issue. Does anyone have an answer to
this question?

TIA.
- quote -

what are my work-arounds for this error when I try
downloading my Fidelity information? Thanks.