Chase OFX: HTTP Error 400: Bad Request

[jmk]

Could it be this issue? This came up recently with several other people:

http://wiki.gnucash.org/wiki/Setting_up_OFXDirectConnect_in_GnuCash_2#Chase_.22username_or_password_are_incorrect.22

Also have a saved message from last year from someone who used these
settings with success:

Bank name: Chase (credit card)
FID: 10898
ORG: B1
Server URL: https://ofx.chase.com
App ID: QWIN
App ver: 2200
Header ver: 102


On 02/03/2016 07:24 AM, Pierre Rochard wrote:
> Hello,
>
> Last week I got my Chase connection working with the new 103 version and
> clientuid. I was able to download transactions for a couple of days.
>
> This week I'm no longer able to do so. I don't think I've changed any
> settings yet I've been getting a 400 error every time I try to connect. I
> had another Chase customer test it and they got this error too.
>
> Has anyone else here been experiencing this? Were you able to find a
> solution?
>
> My settings:
>
> version = 103
> appid = 'QWIN'
> appver = '2500'
> url = 'https://ofx.chase.com'
> org = 'B1'
> fid = '10898'
>
> (I've tested with Gnucash, ofxtools (
> https://github.com/PierreRochard/ofxtools), and MoneyWell.)
>
> Thanks,
>
> Pierre
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.