• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue API Delete Backup not functional

Giu

Basic Pleskian
Server operating system version
Debian 12.4
Plesk version and microupdate number
18.0.58
Hi Forum,

im trying to delete a backup via WP Toolkit API: /api/modules/wp-toolkit/v1/installations/67/backups

in the rest swagger test i receive the following error:

Failed to fetch.
Possible Reasons:

  • CORS
  • Network Failure
  • URL scheme must be "http" or "https" for CORS request.

the request is 100% legit according to the documentation:

curl -X 'DELETE' \
'https://myserver.de:8443/api/modules/wp-toolkit/v1/installations/67/backups?files[]=testdomain.dev__2024-02-01T12_37_48+0100.zip' \
-H 'accept: */*' \
-H 'Authorization: Basic MYBASICAUTH' \
-H 'Content-Type: application/json' \
-d '{
"delete": true
}'


YES:
1) my Auth is valid
2) installation id and filename is valid

in POSTMAN when i do the same request i receive:

Status: "204 No Content" -> but the backup is still on the plesk server so it does not get deleted.

the POSTMAN request:

curl --location --request DELETE 'myserver.de:8443/api/modules/wp-toolkit/v1/installations/67/backups?files%5B%5D=testdomain.dev__2024-02-01T12_37_48%2B0100.zip' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic MYBASICAUTH' \
--data '{
"delete": true
}'

Anyone can help with this issue? im tending of thinking the problem is not on my side - the api endpoint just does not work properly
 
Back
Top