Hello,
I noticed a warning in my TeamSpeak server log.
Every time someone opens the server file system / file browser in the TeamSpeak client, the server writes this warning into the log:
2026-05-23 04:56:27.595015|WARNING |FileListManager| |Could not encode local filename to utf8
2026-05-23 04:56:27.595172|WARNING |FileListManager| |Could not encode local filename to utf8
At the moment I do not notice any real problem in the client or on the server. File browsing seems to work, and there are no visible issues, but the warning appears in the server log.
One special thing about my setup is that the TeamSpeak file storage is on a WebDAV mount, which is mounted with rclone.
Thanks for any help.
This is an issue caused by special unicode characters in the file name. Can you check where exactly they are used?
3 Likes
This is the Unicode en dash:
U+2013
When a folder name contains this character, the TeamSpeak server logs:
WARNING |FileListManager| |Could not encode local filename to utf8
and the affected folder is not shown in the TeamSpeak file browser.
After replacing the Unicode en dash – / U+2013 with a normal ASCII hyphen - / U+002D, the folder appears correctly again.
//Edit:
- the real Unicode character
é / U+00E9 is not shown in the TeamSpeak file browser.
-ü / U+00FC. not shown in the TeamSpeak file browser.
Thanks for the input, I was able to reproduce this with Docker Desktop, however on a default Windows installation it worked fine.
I’ll forward this to the team and if possible will be fixed.
2 Likes