We use 64-bit OS and the latest update didn't fix the issue. I provided more information in the ticket.

I'm sorry, but we currently have no active tickets with relation to FTP issues.

It is possible that you have closed your ticket by mistake, in which case we would need the ticket number in order to find it and reply.

I still like an answer to my previous questions:

1. Why Centova locks out with permanent license? See my previous message about the wrong release date. And why there's no notification for the server admin about the lockout? Why there's no "grace period" or something so that admin could have a chance to take an action (in my case - wait until you fix the problem)?

Centova Cast doesn't "lock out" anymore, since 3.0, after a license check fails, the panel will go into read-only mode -- which means you cannot make changes --, however it will allow your stations to continue normal operations for many days, while you sort out the problem or wait for a fix in case there is a problem with your license on our side.

2. What was the purpose of changing the FTP password handling (or what was changed that introduced all those FTP problems)?

In an effort to keep up with security standards, our developers moved on to use the bcrypt library to encrypt all passwords.

This change worked well across all other components except for Pure-FTP which had fallen behind in supporting bcrypt.

Thanks for your reply.

By "lock out" I mean that netiher admninstrator nor users can make any changes to their streams. This is frustrating, especially when you have "permanent" license.