Restore test: injected fault during the restore, resumed after re-authorization
Injected fault
Injected fault: the check after write-back fails, and the first restore attempt also fails partway. The recovery station requests re-authorization; after re-authorization through the site owner consent page, the restore resumes.
Source: restore test (fault injected on a WP119 test server); no forum thread.
Test setup and what we observed after the failure
Test site: WordPress 7.1, PHP 8.3. The table shows the HTTP status of the homepage and the login page after the recipe recreated the failure.
| Server setup | Homepage | Login page | Note |
|---|---|---|---|
| Apache + PHP-FPM | 200 | 500 | |
| Apache + php-cgi (mod_cgid) | 500 | 500 | |
| Apache + mod_php | 200 | 500 | |
| nginx + PHP-FPM | 500 | 500 |
Outcome of each run
| Date (UTC) | Server setup | Connection mode | Recovery fee | Files and database vs. snapshot | Comment added before the case | Product version | Note |
|---|---|---|---|---|---|---|---|
| 2026-11-12 | Apache + PHP-FPM | FTP | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | Apache + PHP-FPM | SSH | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | Apache + php-cgi (mod_cgid) | FTP | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | Apache + php-cgi (mod_cgid) | SSH | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | Apache + mod_php | FTP | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | Apache + mod_php | SSH | Refunded in full | Differ | Present | 2.1.460 | |
| 2026-11-12 | Apache + mod_php | SSH | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | nginx + PHP-FPM | FTP | Refunded in full | Match except file owners | Present | 2.1.460 | |
| 2026-11-12 | nginx + PHP-FPM | SSH | Refunded in full | Match except file owners | Present | 2.1.460 |
Gaps and the version that fixed them
Every run whose result is not "Matches snapshot", or where the injected fault took effect but the run ended in "Recovered", is listed here: what changed, the version it shipped in, and the re-test date and result.
| Found | Server setup | Connection mode | What we changed | Fixed in | Re-test |
|---|---|---|---|---|---|
| 2026-11-12 | Apache + PHP-FPM | FTP | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + PHP-FPM | SSH | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + php-cgi (mod_cgid) | FTP | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + php-cgi (mod_cgid) | SSH | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + mod_php | FTP | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + mod_php | SSH | Found after the restore: two rows in the options table differed from the snapshot, and the owner of the .htaccess file in the site root changed; the snapshot did not record which rows. A second run the same day differed only in that file owner. No change shipped yet. | In progress | — |
| 2026-11-12 | Apache + mod_php | SSH | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | nginx + PHP-FPM | FTP | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
| 2026-11-12 | nginx + PHP-FPM | SSH | Found after the restore: file contents, permissions and the database matched the snapshot; the owner of the .htaccess file in the site root changed from the site account to the account PHP runs as. No change shipped yet. | In progress | — |
Notes
Runs from the acceptance testing of version 2.1.460 on 2026-11-12, on the small test site. Before each case, two problems were planted on the test site so that the case reaches write-back; the first table shows the HTTP status after that step. Payment in these runs is simulated; the recovery fee column shows the refund the system recorded for that payment. Two further attempts ended before the health check because no recovery station could be created; the health check fee was refunded and the site was not changed. They are not restore tests.
These are records from our test servers, for a given product version on a given day. They are not a promise about the result on any site. Other hosts, PHP versions, and WordPress versions can behave differently.