HTTP-500 Error from Suntrust/Truist

I am receiving HTTP-500 errors as of this morning when I attempt to retrieve for my Suntrust account. I can see from the ConnLog the following:

2021-09-03 13:43:26 +0000 (2021-09-03 06:43:26 PDT): Starting connection to https://ofx-prod-brand.intuit.com/qm2400/fib.dll
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): ConnectionFinished
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Branding completed
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Starting connection to https://www.oasis.cfree.com/fip/genesis/prod/02801.ofx
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Logo download completed
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Logo download completed
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): ConnectionFinished
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Profile completed
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): Starting connection to https://www.oasis.cfree.com/test.ofxgp
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): ConnectionFinished
2021-09-03 13:43:27 +0000 (2021-09-03 06:43:27 PDT): HTTP error 500 from server = <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 500--Internal Server Error</TITLE>
</HEAD>
<BODY bgcolor="white">
<FONT FACE=Helvetica><BR CLEAR=all>
<TABLE border=0 cellspacing=5><TR><TD><BR CLEAR=all>
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error 500--Internal Server Error</H2>
</FONT></TD></TR>
</TABLE>
<TABLE border=0 width=100% cellpadding=10><TR><TD VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New"><FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>Hypertext Transfer Protocol -- HTTP/1.1</i>:</H3>
</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.5.1 500 Internal Server Error</H4>
</FONT><P><FONT FACE="Courier New">The server encountered an unexpected condition which prevented it from fulfilling the request.</FONT></P>
</FONT></TD></TR>
</TABLE>

</BODY>
</HTML>

Is this a temporary issue or a new known problem?

Thanks!
Matt

Comments

This discussion has been closed.