• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the current Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Issue 500 Parse Error with Mail Importer

Aslanj

New Pleskian
Hi all! I've requested further info about the server, but I wanted to see if anyone's getting this error and know the reason for it.

We're seeing a 500 ParseError with the message:
Code:
"syntax error, unexpected 'array' (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST)"
(SessionDirectory.php line 13 is cited.)

...when trying to use Mail Importer (as soon as I click on the icon under any domain.) Domains are all on PHP 8 as far as I can tell, but like I said, I'm waiting on more info regarding the server.

I have access to a "customer" account provided to me via a reseller account. Not really a Plesk person, so apologies for any incorrect terms.

Any direction would be appreciated!
 
It seems that we've not seen this error before. In this case I suggest to please create a support ticket https://support.plesk.com so that an engineer can check this directly on your server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
Thank you, Peter! I'm asking the Plesk license owner to submit a ticket, but they may not have the time to deal with it.

I was also just informed that
Code:
ssh php -v
showed
Code:
7.0.33
and they plan on updating the servers in the next 2-3 months.

However, the extension was working a few weeks ago and the recent (about 2 weeks?) Plesk auto-update may have caused an issue. Hoping someone else will recognize the issue, and if not, I'll post the solution here for reference, if we end up resolving it that is.
 
Hi, did you find a solution? I have the same error running Plesk Migrator on Plesk Onix 17.8.11 after the last Plesk panel update (same PHP version).
 
Is the source server running Plesk Onyx 17.8.11 (meaning that you are migrating from the Plesk Onyx to another server)? If so, what Plesk version and OS is the target server running?
 
The source and destination are both Plesk 17.8.11. I get the error when I try to create a new migration.
Initially I could not access Plesk migrator (I already had migrations configured).
I tried uninstalling and reinstalling Plesk migrator, so now I have no migrations configured.
Entered all the data for the migration and clicked “Prepare,” I get that error.
 
I tried on both servers. Same error. And the same error message appeared before uninstalling/installing Plesk migrator when I was trying to open Migrator.
 
I recommend upgrading or migrating to the most recent Plesk version. Because both Ubuntu 16 and Plesk Plesk 17.8 are have reached the End Of Life (EOL) status long time ago, they are out of support.
 
Back
Top