• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Backup - encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured

AndiS

New Pleskian
Hi,

the backup migration result shows
<message severity="warning" id="0272ed7e-a013-456d-8e6d-015ef7205db5" code="msgtext">
<description>Encoding::encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured. Falling back to ISO-8859-1</description>

for two domains.
The kb article
http://kb.odin.com/en/124608

show a resolution, but how to find the files which are stored with the wrong encoding ?
There is not specific file name listed in the log. Only some id's.

Resolution
Make sure that there are no non UTF8 characters in file names in domain directory /var/www/vhosts/domain.tld/httpdocs. Rename these files and try to backup once again.


Andreas
 
Go to /var/www/vhosts/ and run two commands:

# find . -print | sed 's;[^/]*/;|___;g;s;___|; |;g' > files1.txt
# grep --color='auto' -P -n "[\x80-\xFF]" files1.txt

With first command file files1.txt with all directories structure will be created.
Second command will highlight by red all non-usual symbols in files1.txt
 
Hi Igor,

great. I found a lot of files with german 'Umlauts' which are stored in the wrong encoding.

Andreas
 
Back
Top