Ethan on 27 Jun, 2020 06:33 PM
This is sad news. We had heard that Citi connections were working for everyone for the last few weeks since their last major outage.
For those of you would be willing, could you send us the full contents of your error console in a new private thread? This may contain more detailed information about exactly what's going wrong. We probably only need a few of these to cross reference, so if you're not willing, that's ok.
Here's how to get the logs:
1) In Moneydance, click on the Help menu in the Moneydance menu bar and select the Console Window option. This will open the console messages window.
2) While the Console Window is open, attempt to connect to your bank. Any error messages should be recorded to the Console.
3) Select all of the text in the Console and use the Copy to Clipboard button at the bottom to copy the text.
4) Paste the text from the message window into a text file (preferably saved with a .txt extension) and attach that file to your response.
Again please DO NOT post your logs here or on any public thread, since they may contain your personal account information. Please open up a separate private thread.
This is very strange...I have been having the same problem and had just recently attempted to download and got the same error. After reading this thread and seeing your advice, I opened the Console window and tried again....but this time it worked. I've copied the log and will send in a private message.
I have seen a lot of issues out there with servers here as of late. Makes you wonder what's going on in the cyber security these days or lack there of.. We had an issue last week with IBM Cloud going down and taking out our whole infrastructure in Softlayer.. Even though Citi isn't reporting any issues here https://downdetector.com/status/citi/ the customers are saying they can't login to the mobile app either. I am attaching my log stripped of any personal data but not sure it will tell you a lot so hope it helps in some way.
Ethan on 28 Jun, 2020 05:51 PM
All of the errors we've been seeing over the weekend have this "We've had a problem processing your request. Please try again later" phrase. Are you getting a different error message? If so, can you please open up a new private thread and send us your logs, as I outlined in post 5 on this thread?