On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Error during Plesk upgrade to Obsidian 18.0.37: PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON.

Avatar
Martin Dias
Updated
Follow
Plesk for Linux kb: fixed kb: bug

Applicable to:

  • Plesk for Linux

Symptoms

During a Plesk upgrade to Plesk Obsidian 18.0.37, the following error is shown:

PLESK_INFO: ERROR: Upgrade step 2021-07-01-11-34-45_TrimPlanNames.php failed with code 255 and output:
PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON. in /usr/local/psa/admin/plib/vendor/jms/serializer/src/JsonDeserializationVisitor.php:240

Cause

Product issue:

  • #PPPM-13114 "Upgrading to the latest Plesk Obsidian version no longer sometimes fails with the “PHP Fatal error: Uncaught JMS\Serializer\Exception\RuntimeException: Could not decode JSON, syntax error - malformed JSON.” error."
    Fixed in:

Resolution

Please consider updating your server:

Workaround

If update is not possible for some reason you may try the following

workaround

The error may be safely ignored.

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles