Core update stopped partway: HTTP 500 on the homepage and the login page
站主看到什麼
A WordPress core auto-update stopped before it finished. The homepage and the login page returned HTTP 500 and wp-admin could not be opened. A plain file (/license.txt) still returned 200.
出處（公開論壇帖）: https://wordpress.org/support/topic/wordpress-http-500-error-website-and-admin-login-unavailable/
測試環境與弄壞後看到什麼
測試站：WordPress 7.1、PHP 8.3。下表是照配方弄壞之後，首頁與登入頁回的 HTTP 狀態。
| 主機環境 | 首頁 | 登入頁 | 備註 |
|---|---|---|---|
| nginx + PHP-FPM | 500 | 500 | /license.txt returned 200. |
每一跑的結局
| 日期（UTC） | 主機環境 | 連線模式 | 結局 | 維修站版本 | 備註 |
|---|---|---|---|---|---|
| 2026-11-03 | nginx + PHP-FPM | SSH | Recovered | 2.1.422 | The health check also listed a URL-setting problem that the recipe had not introduced (see gaps). |
| 2026-11-04 | nginx + PHP-FPM | SSH | Recovered | 2.1.427 | Re-test after the change below: the URL-setting line no longer appeared. |
缺口與修在哪一版
結局不是修好的跑次，都在這裡：改了什麼、修在哪一版、重跑的日期與結局。
| 發現日 | 主機環境 | 連線模式 | 改了什麼 | 修在哪一版 | 重跑 |
|---|---|---|---|---|---|
| 2026-11-03 | nginx + PHP-FPM | SSH | With the core files missing, the health check listed a URL-setting problem the site did not have. The check no longer lists it in this state. | 2.1.427 | 2026-11-04 · Recovered |
對到的故障項目
相關錯誤文章
補充
The recipe removes two files under wp-includes and leaves a stale maintenance marker, which is how the forum poster described the site after the interrupted update.
這些是我們測試主機上、某一版、某一天的紀錄，不是對任何網站結果的承諾；其他主機、PHP 與 WordPress 版本的結果可能不同。