Known Issues

• In FileCloud Desktop, when a file inside an Azure or S3 Network Folder is edited, FileCloud erroneously detects a conflict. Therefore, the local version of the file is renamed as a conflict file, and the server version is unchanged. To resolve this, confirm that this is not a legitimate conflict, and rename the local version back to its original name. This issue will be fixed in the future.
  

• In FileCloud Desktop, when an invalid destination path (such as a path with a parameter with invalid characters) is sent for a move or rename operation of a file in an NTFS network, an internal error may occur.

• The latest updates to RHEL 9 have created a licensing issue that impacts all production, trial, and community edition installations of FileCloud running on RHEL 9.
  
  If you are running FileCloud Server on RHEL 9 and perform the latest package update on your Linux installation, FileCloud will be unable to process your currently valid license and will prompt you to update it when you log in to the admin portal. In addition, a license expired message will appear to users when they attempt to log in to the user portal. 
  
  As a workaround, do the following:
  

  1. Open /etc/pki/tls/openssl.cnf

  2. Append the following lines to the end of the file:

     [openssl_init]  
     alg_section = evp_properties
     [evp_properties]
     rh-allow-sha1-signatures = yes 
     

  3. Restart the FileCloud server.

        A permanent resolution to this issue is pending. 

• Known issues with Async (Beta):

  • When Async is running, even if Solr is configured and working, files are not added to the search index.

  • When Async is running, when a file is deleted and then restored, it permanently loses its custom metadata.

  • When Async is running and RabbitMQ is down or restarting, and users continue to upload files, the uploads report success but their background work is lost. The files may not appear in desktop sync clients and are missing from activity and search.
    To avoid this issue, do not use FileCloud while RabbitMQ is down.

  • When Async is running and RabbitMQ is restarted (for example, by Windows Update), if Async is not restarted,
    the first background jobs after the restart fail, and a few notifications or activity entries can be omitted.
    To avoid this issue, restart Async after restarting RabbitMQ.

• Password protected PDF and Office file previews are not showing watermarks. This is an issue with the third-party application used for previewing PDFs, and will be resolved when an update of the application becomes available.
  

• If creation/update of a file in FileCloud via WOPI triggers a move file workflow, the move fails.