• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Forwarded to devs Successful status considered errors by cron taks.

Ahmed

Basic Pleskian
TITLE:
Successful status considered errors by cron taks.​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Ony 17.8.11​
PROBLEM DESCRIPTION:
When an URL call cron task returns a 2xx reponse other than 200, which are also success codes, if it is configured to send notifications only on errors, it will still send a notification as if the run failed.​
STEPS TO REPRODUCE:
Set up a cron task, configured to send a notification only on errors, that returns a 2xx response that is not 200 (for example externally calling the Drupal 8 cron URL returns a 204 status).​
ACTUAL RESULT:
Despite of getting a sucess (2xx) response, the error notification emails are still sent.​
EXPECTED RESULT:
No error notification emails are sent on 2xx responses, that mean success.​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Fixed in Plesk Obsidian as PPP-39206
Please consider an upgrade.
 
Back
Top