Nextcloud not syncing files with unicode characters in their names

Nextcloud version (eg, 20.0.5): 27.0.1
Operating system and version (eg, Ubuntu 20.04): TrueNAS Scale (kubernetes)

The issue you are facing:
After updating and syncing I’m being told that one file will not sync and that Nextcloud will not follow symlinks or sync ignored files.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Try to sync a file named Borreé in E minor.txt, removing the é will allow the file to sync.

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' => 
  array (
    0 => 
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 => 
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
    ),
  ),
  'passwordsalt' => '<redacted>',
  'secret' => '<redacted>',
  'datadirectory' => '/var/www/html/data',
  'dbtype' => 'pgsql',
  'version' => '27.0.1.2',
  'overwrite.cli.url' => '<redacted>',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextcloud-cnpg-main-rw',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'nextcloud',
  'dbpassword' => '<redacted>',
  'installed' => true,
  'instanceid' => '<redacted>',
  'redis' => 
  array (
    'host' => 'nextcloud-redis',
    'password' => '<redacted>',
    'port' => '6379',
  ),
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'upgrade.disable-web' => true,
  'default_phone_region' => 'US',
  'share_folder' => 'Shared',
  'log_type' => 'file',
  'log_type_audit' => 'file',
  'loglevel' => '2',
  'logfile' => '/var/www/html/data/logs/nextcloud.log',
  'logfile_audit' => '/var/www/html/data/logs/audit.log',
  'logdateformat' => 'd/m/Y H:i:s',
  'logtimezone' => 'America/New_York',
  'overwritehost' => '<redacted>',
  'overwriteprotocol' => 'https',
  'activity_expire_days' => '90',
  'trashbin_retention_obligation' => 'auto',
  'versions_retention_obligation' => 'auto',
  'preview_imaginary_url' => 'http://nextcloud-imaginary:9090',
  'enable_previews' => 'true',
  'jpeg_quality' => '60',
  'preview_max_x' => '2048',
  'preview_max_y' => '2048',
  'preview_max_memory' => '1024',
  'preview_max_filesize_image' => '50',
  'onlyoffice' => '',
  'maintenance' => false,
  'trusted_domains' => 
  array (
    0 => '127.0.0.1',
    1 => 'localhost',
    2 => 'nextcloud',
    3 => 'nextcloud-*',
    4 => 'kube.internal.healthcheck',
    5 => 'https',
    6 => '<redacted>',
  ),
  'trusted_proxies' => 
  array (
    0 => '<redacted>',
    1 => '<redacted>',
  ),
  'enabledPreviewProviders' => 
  array (
    0 => 'OC\\Preview\\Imaginary',
    1 => 'OC\\Preview\\BMP',
    2 => 'OC\\Preview\\GIF',
    3 => 'OC\\Preview\\JPEG',
    4 => 'OC\\Preview\\Krita',
    5 => 'OC\\Preview\\MarkDown',
    6 => 'OC\\Preview\\MP3',
    7 => 'OC\\Preview\\OpenDocument',
    8 => 'OC\\Preview\\PNG',
    9 => 'OC\\Preview\\TXT',
    10 => 'OC\\Preview\\XBitmap',
    11 => 'OC\\Preview\\Photoshop',
    12 => 'OC\\Preview\\MSOffice2003',
    13 => 'OC\\Preview\\MSOffice2007',
    14 => 'OC\\Preview\\MSOfficeDoc',
    15 => 'OC\\Preview\\Movie',
    16 => 'OC\\Preview\\PDF',
    17 => 'OC\\Preview\\SVG',
  ),
);

Hello,

I have the same problem with Croatian specific characters “č” “ć” “đ”, but “š” “ž” work ok.

Using NextCloud 27.0 (as plugin in TrueNAS Core) and Windows client 3.9.1. I updated both lately, before discovering the problem. Could be related to either or both.
Both on folder names, and on file names. Old files and folders created and synced before the updates, work just fine.

No info in log on non-synced items, just a sync pending icon or yellow exclamation mark instead of a green checkmark.

Any ideas?

Thanks.

I haven’t found any leads but it’s good to see someone else with the issue, that at least means that it’s not specific to my setup and we can look into opening a bug report.

Seems it’s already been reported here.

UPDATE: All the conversation will be continued in #5935