• 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.

Question UTF-8 compliance of Plesk interface

oana.bota

New Pleskian
Server operating system version
AlmaLinux 8.6 (Sky Tiger), Debian GNU/Linux 11 (bullseye)
Plesk version and microupdate number
Plesk Obsidian Web Host Edition Version 18.0.45
Hi!

We’re testing the UTF-8 compliance of Plesk interface in the following two environment configurations:

Web Server version
OS
Email ServerDatabase
nginx 1.20.2AlmaLinux 8.6 (Sky Tiger)Postfix 3.5.14MySQL 15.1 Distrib 10.3.32-MariaDB, for Linux (x86_64) using readline 5.1
Apache 2.4.54Debian GNU/Linux 11 (bullseye)Postfix 3.5.13MySQL 15.1 Distrib 10.5.15-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper
PostgreSQL 13.7

I mention that we performed the necessary steps so that the web server, DB and Email support UTF-8.

We have tested using a set of native scripts. These are the scripts / languages we tested: Arabic, Cyrillic – Bulgarian, Devanagari – Hindi, Greek, Hangul – Korean, Malayalam, Telugu, Thai, Simplified Chinese, Traditional Chinese, Latin- French.

Passed Tests

We have been able to create Domain Names in these scripts, store and extract data in the above native scripts and publish websites in these scripts.

Failed Tests

We have not been able to create Plesk accounts with credentials in the selected native scripts, DB user accounts with credentials in native scripts, nor email addresses in these scripts.

Are we missing some additional step or is there a workaround that allows us to:
  • Create Plesk users using credentials (username, password) and External email address (mandatory field when creating a Plesk account).
  • Create DB user accounts using credentials in native scripts
  • Create email addresses in native scripts.
Thanks in advance for your support!

Oana
 
Hi!

We’re testing the UTF-8 compliance of Plesk interface in the following two environment configurations:

Web Server version
OS
Email ServerDatabase
nginx 1.20.2AlmaLinux 8.6 (Sky Tiger)Postfix 3.5.14MySQL 15.1 Distrib 10.3.32-MariaDB, for Linux (x86_64) using readline 5.1
Apache 2.4.54Debian GNU/Linux 11 (bullseye)Postfix 3.5.13MySQL 15.1 Distrib 10.5.15-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper
PostgreSQL 13.7

I mention that we performed the necessary steps so that the web server, DB and Email support UTF-8.

We have tested using a set of native scripts. These are the scripts / languages we tested: Arabic, Cyrillic – Bulgarian, Devanagari – Hindi, Greek, Hangul – Korean, Malayalam, Telugu, Thai, Simplified Chinese, Traditional Chinese, Latin- French.

Passed Tests

We have been able to create Domain Names in these scripts, store and extract data in the above native scripts and publish websites in these scripts.

Failed Tests

We have not been able to create Plesk accounts with credentials in the selected native scripts, DB user accounts with credentials in native scripts, nor email addresses in these scripts.

Are we missing some additional step or is there a workaround that allows us to:
  • Create Plesk users using credentials (username, password) and External email address (mandatory field when creating a Plesk account).
  • Create DB user accounts using credentials in native scripts
  • Create email addresses in native scripts.
Thanks in advance for your support!

Oana
any feedback on this?
 
Could you please submit the report via the link below? Thanks!

 
Hi,

I submitted two reports related to this question and they were both removed due to being duplicates. Links to submitted reports are:

We assessed the Universal Acceptance readiness of Plesk and now we are creating the assessment report in which we need to include issues/reports submitted (by us or by other people) that are relevant to our findings.

We would highly appreciate if you provide us with the links of the reports that were accepted by the Plesk Team regarding the two dupliacted reports mentioned above.

Kind regards,
Oana
 
Hi,

I submitted two reports related to this question and they were both removed due to being duplicates. Links to submitted reports are:

We assessed the Universal Acceptance readiness of Plesk and now we are creating the assessment report in which we need to include issues/reports submitted (by us or by other people) that are relevant to our findings.

We would highly appreciate if you provide us with the links of the reports that were accepted by the Plesk Team regarding the two dupliacted reports mentioned above.

Kind regards,
Oana
Links to submitted reports are:
.../threads/creation-of-utf-8-email-accounts-fails.365649/
.../threads/creation-of-db-user-accounts-with-utf-8-credentials-fails.365651/
 
Back
Top