hosting_deployStaticWebsite fails with 500 'Archive not found' — archive_path needs public_html/ prefix

[lowrisk75]

Bug Description

hosting_deployStaticWebsite consistently fails at the deploy trigger step with HTTP 500 and "[Hosting:9999] Archive not found", even though the file upload succeeds.

Root Cause

The hosting_deployStaticWebsite_triggerDeploy method sends:

{"archive_path": "filename.zip"}

But the Hostinger API now requires the full path relative to the account root:

{"archive_path": "public_html/filename.zip"}

Evidence

The file IS uploaded to public_html/ (confirmed via the file browser REST API), but the deploy endpoint can't find it without the public_html/ prefix.

archive_path: "deploy-test.zip"        → 500 "Archive not found"
archive_path: "public_html/deploy-test.zip" → 200 "Request accepted"

Fix

In server.js, function hosting_deployStaticWebsite_triggerDeploy (line ~5025), change:

const deployData = {
  archive_path: archiveBasename
};

to:

const deployData = {
  archive_path: `public_html/${archiveBasename}`
};

Environment

• Package version: 0.1.36
• Hosting plan: hostinger_business_v3
• Tested on: 2026-04-14