• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Problem with special chars after migration between plesks

Iuri Carvalho

New Pleskian
Server operating system version
Ubuntu 22
Plesk version and microupdate number
18.0.59
Hello guys!

We are migrating our sites hosed on Plesk Onyx (Ubuntu 16) to Plesk Obsidian (Ubuntu 22). And we are using to plesk migration tool to do this.

We are having trouble with special chars on the database in the new plesk.

In the old plesk I have this:
mysql> SELECT default_character_set_name, default_collation_name FROM information_schema.SCHEMATA WHERE schema_name = "DB";
+----------------------------+------------------------+
| default_character_set_name | default_collation_name |
+----------------------------+------------------------+
| utf8 | utf8_general_ci |
+----------------------------+------------------------+
1 row in set (0.00 sec)

In the new one, the same database:

MariaDB [DB]> SELECT default_character_set_name, default_collation_name FROM information_schema.SCHEMATA WHERE schema_name = "DB";
+----------------------------+------------------------+
| default_character_set_name | default_collation_name |
+----------------------------+------------------------+
| utf8mb4 | utf8mb4_general_ci |
+----------------------------+------------------------+

When I access the page on the new server, the special chars are like these:

prevenção -> correct: prevenção

Anyone already had this situation?

Thanks in advance.
Kind regards,
Iuri Carvalho
 
Back
Top