• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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