Cannot download from Vanguard

[rkhwaja]

Vanguard is returning an empty string as the body. Since around 7/19/2016, I think.

[jantman]

I can confirm this for me as well, since July 21, 2017 (I think @rkhwaja had the year wrong in his comment).

I run via cron every morning around 2AM Eastern. Vanguard had worked reliably since March through July 20th. From the 21st on, it's getting 0-byte responses.

[jantman]

Ok, I spent about an hour trying various things. The OFX statements that I manually download from Vanguard's site are still OFX version 102, but they include "INTU.USERID" and "INTU.BID" (FITID) fields in the signon, and have the userid in all uppercase. I tried changing the signon to those fields, adding the INTU.BID field, and various different APPVERs for QWIN (2200, 2300, 2400, 2500). I haven't been able to find anything that works. Sometime this week I'll call their tech support and see if I can get any usable information...

[rkhwaja]

Can anyone still download Vanguard ofxs? Maybe it's something to do with the accounts themselves. For instance, I haven't made the switch from mutual fund to brokerage accounts yet and my downloads don't work.

[MarkLodato]

Same here - Vanguard stopped working just as @jantman said. My other bank (PNC) still works fine, so it seems like some change on Vanguard's end.

[rkhwaja]

If I download a new ofx file from the website, my account numbers have the prefix "0540-", whereas I've been using account numbers without that prefix. However, I tried adding the prefix when downloading through ofxclient but it still didn't download a valid ofx.

[jantman]

I found a comment about the PocketSense software, which from what I can tell has a lot of code in common with ofxclient (I believe they're both descended from the same code, or something like that) confirming the Vanguard issue with that code as well.

The author of that code said that he figured out a workaround to fix Vanguard, and the problem seems to be that Vanguard has introduced and is now requiring the use of session cookies, which I'm not sure is really compliant in the OFX spec, but at least the author and one user of that package has confirmed the fix. See this portion of the diff for the fix they used; it seems to try the request once, and if it fails, it resends it with cookies returned in the failure message.

I'm going to try a similar fix in my fork and see if it works.

[jantman]

Ok, I have a quick fix that works. I'm working on getting it polished up and pushed up in a branch and PR now.

[jantman]

I have a PR open ( #47 ) with a fix that works for me, from the vanguard-fix branch of my fork. If anyone would like to give it a try, you can install from that branch with: pip install git+https://github.com/jantman/ofxclient.git@vanguard-fix#egg=ofxclient

[rkhwaja]

Works for me - thanks. I didn't have to make any changes to my login details.

[scanlom]

Good stuff, works now - had to use caps for my username

[captin411]

Thanks for the fix. I’m on vacation for a few more days and this is the first (and only) internet access I’ll have (yes... that far off the grid). I’ll merge it when I get back.

…

On Fri, Aug 4, 2017 at 8:48 AM Michael Scanlon ***@***.***> wrote: Good stuff, works now - had to use caps for my username — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGZk4-gOW6_X5rvyGLvfOHxrBuBV-u-ks5sUz1KgaJpZM4OgPHm> .

[MarkLodato]

Friendly ping. Any chance to merge this fix? Thanks!