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

Error: The uploaded file is not a valid Plesk skin package.

S

sem101

Guest
To test -- I download a default Skin, I open the XML and edit 1 node of text (ex: Date), I repackage and Archive it as a Zip or Tar or Tar.gz, I try to upload Skin archive to test...

Error: The uploaded file is not a valid Plesk skin package.
 
I have make a couple of tests and it seems this feature works perfectly. Here are results of my investigation.

First of all, I downloaded 'Aqua' skin from Plesk CP. After that un-packed it on the server and corrected couple of fields:

<VERSION>1.0.1</VERSION> - changed
<DATE>2007-03-22</DATE> - changed

After that packed this info .tgz archive and tried to upload but failed with the same error. As I figured out further I just forgot to use '-z' option during packaging. So correct command was:

# tar -czf Aqua1.tgz *

Here I got package Aqua1.tgz. When I tried to upload it I got next message:

Error: The skin 'Aqua' already exists

So I had to change also following fields in info.xml file:

<NAME>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>
</NAME>
<DESCRIPTION>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>
</DESCRIPTION>
<KEYWORDS>
<LOCALESTRING language="en">Aqua1</LOCALESTRING>

Then I re-packed the package and was upload to upload it successfully.

Checked me changes and can see that all information have been saved correctly.

Hope this information helps.
 
Thank you, I will continue to try again. But I did exactly what you did and still received the error. I'll post back here if it persists.
 
Back
Top