• 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 WP-Toolkit not finding updates when APCu Manager plugin is active

BreatheTech

New Pleskian
Server operating system version
Almalinux 10.2
Plesk version and microupdate number
18.0.79 #3
Hi
I seem to be having an issue where wordpress sites with the APCu Manager plugin activated are not seeing updates in WP-Toolkit. Refreshing in WP-Toolkit doesn't find any new updates - not for plugins or themes or wordpress core. As soon as APCu Manager is deactivated WP-Toolkit suddenly sees the available updates. This is impacting all the wordpress instances on the server.

Note that wordpress itself (when logged into wp-admin) DOES see that updates are available when APCu is running.

APCu Manager is working correctly and php_info shows apcu enabled correctly

Does anyone have any ideas/suggestions for how to resolve this (other than disabling APCu)

This is the latest Plesk (18.0.79 #3) on Almalinux 10.2 with sites running on pure nginx, with PHP-FPM 8.5.8 and mariadb 10.11.18

Cheers
 
Hi, @BreatheTech . I was unable to replicate the behavior by enabling APCu and activating the APCu Manager plugin alone. WP Toolkit still detects Updates properly:

I can see that there's an open support ticket with our team and our engineers were also unable to replicate the behavior on test environment. It will be great if you can provide them with direct server access for further investigation.
 

Attachments

  • Screenshot 2026-07-21 184107.png
    Screenshot 2026-07-21 184107.png
    193.9 KB · Views: 2
Hi
Thanks for looking into this Sebahat
With the APCu Manager plugin once it is activated you have to go into its settings and tick the box to actually enable the caching - otherwise it's not actually doing anything. Perhaps that is why it wasn't possible to reproduce the issue?
1784649109342.png
 
@BreatheTech , thank you for the clarification. For some reason, I was under the impression that's activated by default. I have now enabled it, and I was indeed able to replicate the behavior. I have opened an internal report for our team to review the matter further. I will follow up with more details as soon as possible. Thanks for your patience in the meantime.
 
Our team created a bug identified with ID EXTWPTOOLK-14811 to correct the behavior of WP Toolkit calling APCu. Until a fix for the bug is introduced the solution our team suggested is:

1. Create a backup of the current acpu.ini file:

Code:
cp /opt/plesk/php/8.4/etc/php.d/apcu.ini /root/apcu.ini.bak

Where 8.4 corresponds to the PHP version assigned to the WordPress website.

2. Enable APCu for cli by running the following:

Code:
echo -e "apc.enable_cli = 1\napcu.enable_cli = 1" >> /opt/plesk/php/8.4/etc/php.d/apcu.ini

3. Refresh the affected Wordpress instance(s) following these instructions.

Thank you for bringing our attention to the issue.
 
Back
Top