I guess some lines are in the wrong date/time order. Sometimes it happens but such situation is not expected by Plesk log browser - so looks like a bug.
@Maris , could you open your log file as is (e.g. via file manager viewer) and match line order with their date/time fields?
Hello @Maris
I cannot reproduce the issue at the same OS and Plesk version. Please provide more details. Is it occurred during real-time updates mode? Does the issue persist after the page reloads?
Hello @msf grg
Expiration date is a limit. So just replace [placeholders] with your values:
<packet>
<webspace>
<set>
<filter>
<id>[YOUR_SUBSCRIPTION_ID]</id>
</filter>
<values>
<limits>
<limit>
<name>expiration</name>...
Hello @Lutuh
REST API is quite new feature. It was implemented in Plesk Onyx 17.8 and works out of the box.
See documentation for details About REST API
Hello, @xdelios
DB is ok, repository column should be specified.
How your Scheduled Backup Settings screen looks like? What repository option do you select?
Everything is right here. I'll try to reproduce issue at my test server.
Can you provide any additional details like is it local backup or FTP and so on?
Please, check content and permissions for scheduled backup cron job:
ls /etc/cron.d/plesk-backup-manager-task
cat /etc/cron.d/plesk-backup-manager-task
Is it ok?