
I think the only hope for this app is to be rewritten from scratch. The problems are many, random, impossible to reproduce, and therefore impossible to report. And the crashes, for reasons unknown to me, don't show the macOS crash report dialog that you normally see. The worst part is, the "unknown error" alerts happen entirely randomly, there is no way to reproduce the bug, so it's impossible to report it to the dev. It's incredibly frustrating and rather than aiding me at doing my job, it makes it even more frustrating. Ocassionally it will randomly give you "unknown error" alerts and you will be BOMBED with them (you really have to dismiss hundreds of them at a time - one by one). It crashes all the time for no apparent reason. A few months ago I started doing heavy SSH and FTP related work, mostly with moving files around in a server.

as they're not used on instance 1.I bought this app many years ago and I used it ocassionally for light FTP tasks. So I am not 100% how it should have been set up correctly or what I need to look at to rectify this, but would really appreciate if someone could assist and let me know what I need to look at within WHM in order to just be able to connect to accounts without any additional certificates etc. The server may be down, or your network may not be properly configured." pem certificate attached in CyberDuck (which I don't want to have to do for each account), and then connecting to the third account which I have created today will connect but not list the directory and times out - "Operation timed out.

Please contact your web hosting service provider for assistance.", connecting to the second account seems to work but I notice it has a.

Exhausted available authentication methods. It has 3 accounts at present, connecting to one of them gives me "Login failed. However on the other, I am having great difficulty. On one of the instances I can access each account individually via FTP no problem at all. So I have 2 x AWS EC2 instances, both running WHM/cPanel, and both set up identically (or so I thought) following this guide: Launch an AWS™ AMI™ Instance | cPanel & WHM Documentation
