Customizing Plesk with a branded theme can enhance your client experience and reinforce your company identity. However, installing custom branding themes isn\u2019t always straightforward. One common issue is the Plesk Error: meta.xml was not found in archive error.<\/p>\n\n\n\n
When you try to install a theme using the Plesk CLI:<\/p>\n\n\n\n
plesk bin branding_theme -i -vendor admin -source \/path\/theme-file.zip<\/code><\/pre>\n\n\n\nYou might encounter:<\/p>\n\n\n\n
Meta information file meta.xml was not found in archive.\nexit status 1<\/code><\/pre>\n\n\n\nEven though your ZIP contains a meta.xml file, Plesk is unable to detect it. This typically happens because of incorrect ZIP structure, file permissions, or invalid XML syntax.<\/p>\n\n\n\n
Step 1: Check the ZIP Structure<\/strong><\/h2>\n\n\n\nPlesk expects a very specific structure for branding themes. The meta.xml file must be at the root level<\/strong> of the archive:<\/p>\n\n\n\ntheme-file.zip\n\u251c\u2500\u2500 meta.xml\n\u251c\u2500\u2500 css\/\n\u2502 \u2514\u2500\u2500 custom.css\n\u251c\u2500\u2500 icons\/\n\u2514\u2500\u2500 images\/<\/code><\/pre>\n\n\n\nYou can verify the structure using:<\/p>\n\n\n\n
unzip -l \/path\/theme-file.zip<\/code><\/pre>\n\n\n\nIf meta.xml is inside a subfolder, like theme-file\/meta.xml, Plesk will fail to find it.Fix:<\/strong> Move all files to the root of the ZIP and repackage:<\/p>\n\n\n\ncd \/tmp\nunzip \/path\/theme-file.zip -d theme-file\ncd theme-file\nmv theme-file\/* .\nrm -rf theme-file\nzip -r \/path\/theme-file.zip .<\/code><\/pre>\n\n\n\nStep 2: Validate meta.xml<\/strong><\/h3>\n\n\n\nmeta.xml must be valid XML format and include required fields:<\/p>\n\n\n\n
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<meta>\n <name>theme-file<\/name>\n <description><\/description>\n <version>1.0.0<\/version>\n<\/meta><\/code><\/pre>\n\n\n\nEven a small syntax error can prevent Plesk from recognizing the theme.<\/p>\n\n\n\n
Step 3: Check File Permissions<\/strong><\/h3>\n\n\n\nEnsure the ZIP file is readable by Plesk:<\/p>\n\n\n\n
chmod 644 \/path\/theme-file.zip<\/code><\/pre>\n\n\n\nStep 4: Install the Theme<\/strong><\/h2>\n\n\n\nOnce your ZIP is correctly structured and permissions are set, install the theme:<\/p>\n\n\n\n
plesk bin branding_theme -i -vendor admin -source \/path\/theme-file.zip<\/code><\/pre>\n\n\n\nIf everything is correct, Plesk<\/mark><\/a> will install your theme without errors.<\/p>\n\n\n\nConclusion<\/strong><\/h3>\n\n\n\nInstalling custom Plesk branding themes is simple once you understand the expected ZIP structure, XML requirements, and permissions. By ensuring that meta.xml is at the root level, validating your XML, and checking file permissions, you can avoid the common meta.xml not found error and successfully deploy your custom theme.<\/p>\n\n\n\n
If you’re facing issues like the Plesk Error: meta.xml was not found in archive, our expert team at Skynats can help you quickly identify and resolve the problem. With our Server Management Services<\/a> and Hourly Server Support Services<\/a>, we provide reliable troubleshooting and control panel management to ensure smooth server operations.
Contact Skynats today to get instant professional assistance and restore your Plesk environment without downtime.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Customizing Plesk with a branded theme can enhance your client experience and reinforce your company identity. However, installing custom branding themes isn\u2019t always straightforward. One common issue is the Plesk Error: meta.xml was not found in archive error. Understanding the Problem When you try to install a theme using the Plesk CLI: You might encounter: […]<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[1152,1150,530,1151,302],"class_list":["post-16552","post","type-post","status-publish","format-standard","hentry","category-blog","tag-hourly-server-support-services","tag-meta-xml","tag-plesk-error","tag-plesk-error-meta-xml","tag-server-management-services"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/16552","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=16552"}],"version-history":[{"count":1,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/16552\/revisions"}],"predecessor-version":[{"id":16555,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/16552\/revisions\/16555"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=16552"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=16552"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=16552"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}