• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue WP customize preview getting error 500

Space Monkey

Basic Pleskian
Server operating system version
Ubuntu 22
Plesk version and microupdate number
18.0.62
As at Vultr de plesk admin SE is eol I took one big server and transferred all my sites to that server with Plesk Pro. Migrating went easy but now on every site I have little kinks, for the most part I could figure out what the issue was.

But at one of my sites, in the WordPress customizer the preview doesn't load, I get a 500 error, when I click the home page I will see my site but any customization I do will not be instantly show where it normally should.

I checked the log but can't figure it out. It's allocated more than enough memory.

My other sites don't have this issue but have other weird things going on.

Anything comes to mind?
 

Attachments

  • e5.png
    e5.png
    48.8 KB · Views: 4
As at Vultr de plesk admin SE is eol I took one big server and transferred all my sites to that server with Plesk Pro. Migrating went easy but now on every site I have little kinks, for the most part I could figure out what the issue was.

But at one of my sites, in the WordPress customizer the preview doesn't load, I get a 500 error, when I click the home page I will see my site but any customization I do will not be instantly show where it normally should.

I checked the log but can't figure it out. It's allocated more than enough memory.

My other sites don't have this issue but have other weird things going on.

Anything comes to mind?
I had the similiar issue, and mine is solved following this thread:

 
Back
Top