Same for me with Wells Fargo. Header to the message noted above is
"There was an error communicating with your financial institution. The details to this error are below." Followed with bank name, account name, and account number, and then the above message (" ... communication or parsing error ...")
A communication or parsing error occurred. This could be the result of a network problem, a proxy error, or misconfigured server.
Error Description: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
Ian O on 11 Jul, 2018 12:41 PM
Sorry to hear of the issue you have all encountered while using Moneydance. The cause for what you're seeing is your bank have retired one of their older certificates which has broken the connection in Moneydance.
The latest preview version of Moneydance 2017 contains the certificates that will allow you to connect. Take a manual backup of your data file via File --> Export Backup, then download the preview version of Moneydance from here.
Before upgrading, I'd recommend checking if your license key is valid for use with Moneydance 2017. You can do this by entering your license key in the 'Upgrading?' box on this page.
You should be able to locate your license key within Moneydance by navigating to Help --> About Moneydance (Moneydance --> About Moneydance on Mac).
If you don't see a license key displayed, you may have purchased from Apple. Those who purchase from Apple will need to wait for the next stable version of Moneydance to be pushed to the Apple AppStore.
If you would prefer to wait for the improvements included in the preview version to reach stable release, please let me know and I'll make sure you're notified.
I am up and working BUT it was NOT a piece of cake. I run Manjaro Linux (ARCH derivative) and was VERY hesitant to install as you direct in "Other Linux Distributions". Your install script was suspiciously HUGE, as in many, many gigabytes -AND- contained binary data. I did NOT want to run it - I didn't trust it, to be frank. Instead I installed the correct way for an ARCH-based system and I created an install package (took about an hour because I rarely do it). After a couple of hiccups I am working and Moneydance again works works Wells-Fargo. To help any other ARCH users I have attached the PKGBUILD
on 11 Jul, 2018 11:22 PM
I have the same problem-- unable to download transactions from my bank. I'm using a Mac and purchased Moneydance via the Apple App Store. Bank staff unable to answer any useful questions whatsoever, but, it doesn't look like they could help anyway, since, there doesn't seem to be any way to upload new certificates from the bank into Moneydance. Suggestion for the future: perhaps the certificates could be stored in the macOS Keychain, so that new certificates could be loaded without having to build and install a new version of Moneydance just to install the new certificates?
I am having the same issue. I purchased the 2017 version last year and your site indicated I was entitled to a free upgrade with my license key. I installed that and I am receiving the same error message.
Downloaded the new unreleased? version and the Wells Fargo connection now works. I have a problem with Schwab now but I think I know how to fix that. Please let us know when the new version is officially released.
As this stage of the life of Moneydance 2017 I consider that what are described as "Preview" releases are really incremental bug fix releases - you do not often see new features being made available at this stage of a products life.
What ever version becomes the next "Stable" release will just be a consolidate patch release. From what I have observed a release becomes a candidate for being described as a stable when it has been available for a while without any intervening problems arising.