• 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 Unexpected token t in JSON at position 374

srib

New Pleskian
Server operating system version
Ubuntu 16.04.7 LTS
Plesk version and microupdate number
18.0.34
Seeing the following message under a few domains on my Plesk:
Unexpected token t in JSON at position 374
1731476068629.png
Running Plesk Obsidian 18.0.34 Update #2 (last updated in 2021).

Trying to update packages, receiving an error: Unable to receive update information for th epackage(s)

1731476177691.png

Looks like we are on a very old and out of date Plesk that is having issues. What is the best way to get out of this?

-Sri
 
Hi, Ubuntu 16 is already out of support since quite long (2021).
Here, probably the best would be to migrate to an up-to-date OS and see if that still works even with the issues you're experiencing.

Should you have issues during the migration, I would suggest reaching out to our support team.
(Use the license from the new system to open the request, as old OSes will not be accepted)

Here I in the best case is just some corrupted file, or the server got hacked due to being so out of date with no security patches from OS, etc.
 
Back
Top