• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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