Description
After updating the plugin from 2.4.3 to 2.4.4 on two separate WordPress sites, manual and automatic cache purging both fail with the notice:
The Hestia Nginx Cache could not be purged!
Both sites were working correctly with 2.4.3 immediately before the update, with no other configuration changes made (same Access key, Secret key, hostname, port, username, and domain settings).
Steps to reproduce
- Have a working Hestia Nginx Cache setup on 2.4.3 (purge working normally).
- Update the plugin to 2.4.4.
- Trigger a manual purge from the admin bar or plugin settings page.
- Observe the "could not be purged" notice.
Environment
- Plugin version: 2.4.4 (previously working on 2.4.3)
- WordPress version: [à compléter]
- PHP version: [à compléter]
- Hestia Control Panel version: [à compléter]
- Affected on: 2 sites, same server / same HestiaCP instance (self-hosted HestiaCP + Nginx)
- Behavior: reproducible on both sites, consistently
What I've already checked
- Access key / Secret key unchanged and still valid
- API access enabled, allowed IPs (127.0.0.1 + server public IP) correctly set
- Hostname/port settings unchanged from the working 2.4.3 config
- Domain to purge field unchanged
- No Cloudflare in front of these sites
Expected behavior
Purge should succeed as it did on 2.4.3, since no configuration was changed — only the plugin version.
Additional context
Changelog for 2.4.4 mentions "Fix warnings & errors from Plugin Check" — could this refactor have inadvertently broken the API call/response handling? Happy to provide debug logs, a network capture of the API request, or test a patched build if useful.
Merci
Description
After updating the plugin from 2.4.3 to 2.4.4 on two separate WordPress sites, manual and automatic cache purging both fail with the notice:
Both sites were working correctly with 2.4.3 immediately before the update, with no other configuration changes made (same Access key, Secret key, hostname, port, username, and domain settings).
Steps to reproduce
Environment
What I've already checked
Expected behavior
Purge should succeed as it did on 2.4.3, since no configuration was changed — only the plugin version.
Additional context
Changelog for 2.4.4 mentions "Fix warnings & errors from Plugin Check" — could this refactor have inadvertently broken the API call/response handling? Happy to provide debug logs, a network capture of the API request, or test a patched build if useful.
Merci