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

Forwarded to devs Domain disabled but uutomated tasks still called

FreeUserName

New Pleskian
TITLE:
Domain disabled but automated tasks still called
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
‪CentOS Linux 7.2.1511 (Core)‬
Plesk Onyx Version 17.5.3 Update #46, last updated on April 24, 2018 03:08 AM
PROBLEM DESCRIPTION:
When a domain is disabled I would expect the Automated Tasks / Cronjobs setup in that disabled domain are also disabled. This is not the case. In my example I was calling a PHP script on the disabled domain. This fails and an error report is sent (enabled this). If you call an external url or maybe a script directly without url it could be your automated task keeps on running and execute tasks even when your domain is disabled.

I would vote for also disable the Automated Tasks on domain disable.​
STEPS TO REPRODUCE:
Disable domain with automated tasks setup
Test after the domain is disabled if the task is still called (is the case)​
ACTUAL RESULT:
Errors on automated tasks if url is called that is disabled. Probably no error when external url is called from disabled domain or local script.​
EXPECTED RESULT:
No errors and automated tasks not running on disabled domains.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Thank you for the report. Actually, we have already request PPPM-4560 about this issue. As far as I know, this request is considered to be implemented in Plesk 17.9 version.
 
Back
Top