• 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.

Resolved Oops! We ran into some problems.

What's the reason you need Redis? It's only useful on dynamic websites that have lots of visitors.
I found that using W3 Total Cache makes a WordPress site much faster without using an object cache like Redis or Memcached.
Running a WordPress site on Nginx instead of the combo Nginx + Apache also makes it faster and uses less memory.
 
Thanks for the recommendation, the reason why I'm using Redis is that I'm running a member site, which hopefully will have lots of visitors.
Interesting info about running a WordPress site on Nginx instead of the combo Nginx + Apache.
 
I limited the memory for Redis in Docker, from Unlimited to 2000mb as a starting point for my 8gb server.

This solved the issues in Redis Console Log, which now loads instantly without time out, and the log is a lot shorter.

I have no idea if 2000mb is to little or too much to allocate for a 8gb server, but it seems like a good starting point.
 
Back
Top