Ah good catch. I run EM releases so I hadn't seen this was out yet.

Definitely reach out to the WRC - another "educated" guess from me on potential causes would be filesystem fragmentation. I've seen that cause databases to fail to expand in the past.

Can Nessus tell you what in particular is allowing the use of those ssl ciphers? Are you sure it's HealthShare that's causing the issue? Where in HealthShare did you disable the lower TLS version?

It's already been reported, I meant! Rest assured.

I would go straight to support for this to be honest! They can look at the contents of IRISTEMP with you to help figure out why there's leftover data there.

How are you trying to access the ftp link? I tested and it should be publicly available. Try pasting the link into your file explorer on Windows, for example.