Why do File Cloud Gateway connections only support UTF-8 encoding?

Last modified date: 2022-12-21

Most cloud services only support UTF-8 encoding, so HybridMount File Cloud Gateway connections only support UTF-8 encoding for wide synchronization compatibility with cloud services.

File Station, SMB, and WebDAV protocols work with File Cloud Gateway connections because they use UTF-8.

However, if you use FTP or NFS protocols to access File Cloud Gateway connections and your file or folder names contain non UTF-8 characters, HybridMount will prevent non UTF-8 files or folders from being uploaded to cache spaces and cloud services.

By default, Windows NFS client does not support UTF-8 encoding, so you cannot access File Cloud Gateway connections via Windows NFS client. However, Windows provides a beta option in Region Settings to enable UTF-8 encoding:

If you select this option, you can use Windows NFS client to access File Cloud Gateway connections, because Windows use UTF-8 instead of other non-Unicode encoding.

Important: Beta settings are intended for testing purposes. When applied, this setting may alter path names, causing some applications to stop working normally.

Was this article helpful?

Yes. No.

For further assistance, ask other users and QNAP experts in the community. Go to QNAP Community

Please tell us how this article can be improved:

The article is missing important information
The article's solutions do not work
The article is too complicated
The article contains incorrect information
The article is out-of-date

If you want to provide additional feedback, please include it below.