Title: WordPress install API endpoint returns success but installation never completes
Example website: progaragedoorporterranch.com
Description:
Using the Hostinger API installWordPress endpoint (v1) to provision WordPress on newly created addon domains. The API consistently returns a success response ({"message":"Request accepted"}), but no WordPress installation is ever created — confirmed by querying the corresponding "list WordPress installations" endpoint, which returns an empty array even after multiple retries and wait periods of 60–90+ seconds between attempts.
Steps to reproduce:
Create a new addon domain under an existing hosting account via the createWebsite endpoint (succeeds, domain shows as active/enabled).
Call the installWordPress endpoint for that domain with valid credentials, site title, and overwrite: true.
API responds with success (Request accepted).
Query the listWordPressInstallations endpoint for that domain — returns an empty result.
Repeat steps 2–4 multiple times over an extended period (confirmed persisting over 30+ minutes) — installation never appears.
Expected behavior:
A successful API response should result in an actual WordPress installation being created and queryable shortly afterward.
Actual behavior:
The API accepts the request and returns success, but the install job silently fails or never runs on the backend. No installation record is ever created for the affected domain.
Additional context:
This occurred for 11 domains created on the same day, all under the same hosting account.
10 other domains created on an earlier date under the identical account, using the identical request structure, installed successfully without issue.
The domain, credentials, and account are all confirmed active and correctly attached (verified via listWebsites endpoint).
Support was consulted and confirmed the account/domain setup is correct, and that this appears to be an install-job issue on the backend rather than a request formatting issue.
No errors are surfaced anywhere in the API response — the failure is silent.
Impact:
Blocks bulk WordPress deployment workflows that rely on this endpoint completing reliably after a success response.
Title: WordPress install API endpoint returns success but installation never completes
Example website: progaragedoorporterranch.com
Description:
Using the Hostinger API installWordPress endpoint (v1) to provision WordPress on newly created addon domains. The API consistently returns a success response ({"message":"Request accepted"}), but no WordPress installation is ever created — confirmed by querying the corresponding "list WordPress installations" endpoint, which returns an empty array even after multiple retries and wait periods of 60–90+ seconds between attempts.
Steps to reproduce:
Create a new addon domain under an existing hosting account via the createWebsite endpoint (succeeds, domain shows as active/enabled).
Call the installWordPress endpoint for that domain with valid credentials, site title, and overwrite: true.
API responds with success (Request accepted).
Query the listWordPressInstallations endpoint for that domain — returns an empty result.
Repeat steps 2–4 multiple times over an extended period (confirmed persisting over 30+ minutes) — installation never appears.
Expected behavior:
A successful API response should result in an actual WordPress installation being created and queryable shortly afterward.
Actual behavior:
The API accepts the request and returns success, but the install job silently fails or never runs on the backend. No installation record is ever created for the affected domain.
Additional context:
This occurred for 11 domains created on the same day, all under the same hosting account.
10 other domains created on an earlier date under the identical account, using the identical request structure, installed successfully without issue.
The domain, credentials, and account are all confirmed active and correctly attached (verified via listWebsites endpoint).
Support was consulted and confirmed the account/domain setup is correct, and that this appears to be an install-job issue on the backend rather than a request formatting issue.
No errors are surfaced anywhere in the API response — the failure is silent.
Impact:
Blocks bulk WordPress deployment workflows that rely on this endpoint completing reliably after a success response.