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

Issue Problems with Scheduled Tasks

Charly_dog

New Pleskian
Operating system Debian 8.11
Product Plesk Onyx
Version 17.8.11 Update # 45, last updated: Mar 12, 2019 07:12:14

Hello, I recently have a problem with scheduled tasks
I would like to create a new task to carry this cron job
wget -qO- 'https://xxxxx.com/cron/task/run?key=3FSE@' &&> / dev / null
with comfortable execution as * * * * *

but Plesk gives me the message
The task "wget -qO- 'https://xxxxx.de/cron/task/run?key=3FSE@' &&> / dev / null" was completed in 0 seconds, but errors occurred.
/ bin / sh: 1: wget -qO- 'https://xxxxx.de.de/cron/task/run?key=3FSE@' &&> / dev / null: not found

then I have it with me
"cd /var/www/vhosts/xxxxx.de/httpdocs/app/ & Console / cake cron run 3FSE @"
tries
here also the error message
Could not open input file: "cd /var/www/vhosts/xxxxx.de/httpdocs/app/ & Console / cake cron run 3FSE @"

I am now a bit overwhelmed, especially since these have worked for months without problems
does anyone have an idea and can help thank you
 
old thread but I was facing a similar issue.

So first run the command as wget https://plesk.com/cron

remove quite, dev/null to see output

now in my case it was showing ssl certificate error for server ip, ssl is valid for domain but it was not working. So I used --no-check-certificate and its working.

--no-check-certificate bypasses ssl verification check so use it carefully and may be fix the ssl issue if possible.
 
Back
Top