• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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