Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Unfortunatly, this command runs well with ssh but not within task Plesk scheduler…
Is there a way to create a routine by ssh, I mean to schedule a recursive task (like Plesk scheduler…), each day for instance ?
Should it do the job :
# Download data every night at 7:25 pm
25 19 * * * wget https://xxxxx/list.json -P /var/www/vhosts/<domain>/httpdocs/wp-content/uploads/files -O attendee.json
Okay, I think I got it. I Tested this successfully in the Plesk scheduler: wget -O httpdocs/wp-content/uploads/files/attendee.json https://example.com/list.json
Task "wget -O httpdocs/wp-content/uploads/files/attendee.json https://example.com/list.json completed with error in 0 seconds, output:
httpdocs/wp-content/uploads/files/attendee.json : No such file or directory
No, if you are running the scheduled task via Website & domains > Site dashboard > Scheduled Tasks then you don't need to include the full path, because the scheduled task runs from the home directory of the domain (system) user. But you can give it a try of course.
For me wget -O httpdocs/wp-content/uploads/files/attendee.json https://example.com/list.json works, when it test it.
The No such file or directory error indicates an issue with directory. Does the directory files actually exist?
Ok, I ve fixed permissions
But, always the same error than before :
Connecting to REMOTE-SERVER.. connected.
ERROR: The certificate of 'exemple.com' is not trusted.
ERROR: The certificate of 'exemple.com' doesn't have a known issuer.