Let's Encrypt could not be started. String could not be parsed as XML

Created:

2016-11-16 13:12:22 UTC

Modified:

2017-08-08 13:37:12 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Let's Encrypt could not be started. String could not be parsed as XML

Applicable to:

  • Plesk 12.5 for Linux

Symptoms

The following error occurs while accessing Plesk > Extensions > Let's Encrypt :

    ERROR: Exception
String could not be parsed as XML

The following occurs under /var/log/sw-cp-server/error_log :

2016/02/12 04:47:51 [error] 31549#0: *24 open() "/usr/local/psa/admin/htdocs/modules/letsencrypt/javascript/prototype.js" failed (2: No such file or directory), client: 1.2.3.4, server: , request: "GET /modules/letsencrypt/javascript/prototype.js?1440594988 HTTP/1.1", host: "hostfh.domain.tld:8443", referrer: "https://hostfh.domain.tld:8443/modules/letsencrypt/"

Also in /var/log/plesk/panel.log :

    [12-Feb-2016 15:47:28 America/New_York] PHP Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xF6 0xA0 0x5F 0x4C; File: /usr/local/psa/admin/plib/pm/ApiRpc.php, Line: 72

[2016-02-12 15:47:28] ERR [1] Exception: PHP Warning: SimpleXMLElement::__construct(): Entity: line 2: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xF6 0xA0 0x5F 0x4C; File: /usr/local/psa/admin/plib/pm/ApiRpc.php, Line: 72

Cause

FTP user's passwords contain non-utf symbols.

Resolution

The following procedure should be done for all domains and all FTP users:

  1. Go to Plesk > Domains > domain name > FTP access > name of user
  2. Set a new password.
  3. Click "OK"
Have more questions? Submit a request
Please sign in to leave a comment.