For general information:

FTPS:
After the above upgrade I had to recreate our FTPS-connections. I tried to fix the existing with no luck. After creating new connections with the same settings it worked.

SFTP:
Our connections using public/private key no longer worked because VisualCron now has its own repository which is nice. I imported the certificates and added them to the specific connections and it worked again.

Thanks for this info as I am prepping to upgrade. I will be interested to hear from support on if this is a bug that the connections were not converted to the new method correctly. I don't believe you should have to recreate them when upgrading.

Agree.

VisualCron is a wonderful and complicated piece of software. I like the willingness to refactor and the frequent update cycle. But too often objects stop working and need fixes after upgrades. Having more and more logic put into the program, upgrades become more and more risky. A more thorough upgrade testing would be much appreciated!

I might have overlooked some info in this particular case, but I would have saved some frustrating hours if ie. a pop up had told me, that SFTP connections with external certificate files needed some action, and that I was better off recreating my FTPS connections.

For general information:

FTPS:
After the above upgrade I had to recreate our FTPS-connections. I tried to fix the existing with no luck. After creating new connections with the same settings it worked.

SFTP:
Our connections using public/private key no longer worked because VisualCron now has its own repository which is nice. I imported the certificates and added them to the specific connections and it worked again.

Thanks for this information. Yes, we reworked the key-functionality to improve it and have it internally stored.

Regarding the FTPS connection- I'm going to see if I can reproduce that issue. Were you using any credential to access the FTPS connection? Or in the task, if you did, it could be that you had to re-select the credential for it to work

---

The credential section was greyed out in the anonymous connection. We also have a connection with credentials, and I think I was able to change the settings there. But both didn't work and needed to be created from scratch again.

The error in both cases was SSL 75788: which means that the certificate was bad. But it is the exact same certificate that worked when creating a new connection that worked.