Unable to reconfigure domain in punycode: A label does not meet the IDNA BiDi requirements (for right-to-left characters)

Created:

2017-06-02 05:08:38 UTC

Modified:

2017-08-16 16:20:13 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Unable to reconfigure domain in punycode: A label does not meet the IDNA BiDi requirements (for right-to-left characters)

Applicable to:

  • Plesk Onyx for Windows

Symptoms

  • There is a domain created in punycode xn--mgbh0fb.com .

  • It is possible to create a domain alias for this domain in Plesk, however, alias creation in IIS fails with the error:

    A label does not meet the IDNA BiDi requirements (for right-to-left characters).
    
  • The following error appears when reconfiguring this domain via CLI:

    Unable to convert a whole domain name 'xn--mgbh0fb.com.203-0-113-2.example.hostname.com' into its
    Unicode form for human-readable display. IDNA error bit set: 2048
    A label does not meet the IDNA BiDi requirements (for right-to-left characters).

       at getIdnHost(xn--mgbh0fb.com.203-0-113-2.example.hostname.com)(getIdnHost line 114)
       at updateBindings(xn--mgbh0fb.com)(WebServerAdapter::updateBindings line 547)
       at configHosting(xn--mgbh0fb.com)(WebServerAdapter::configHosting line 476)
       at configHosting(xn--mgbh0fb.com)(WebServerManager::configHosting line 3022)
       at execute console command --reconfigure-vhost(vconsoleapp::start line 122)
       at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin64\websrvmng.exe" --reconfigure-vhost "--vhost-config=tmp 6CD3.tmp" "--config="(vconsoleapp::run line 139)
    (Error code 1)

Cause

The issue is caused by Plesk bug with id #PPPM-6387 . It is planned to be fixed in future updates.

Resolution

For Plesk Onyx 17.0 the following workaround can be applied:

  1. Download websrvmng.exe.zip and unzip it.

  2. Create a backup of the original websrvmng.exe at %plesk_dir%admin\bin64\ .

  3. Place the unzipped websrvmng.exe to %plesk_dir%admin\bin64\ .

Warning: This workaround is not applicable for Plesk Onyx 17.5

Attachments:

Have more questions? Submit a request
Please sign in to leave a comment.