joomlaupdate/healthcheck
HTTP Status code 400 bad request for invalid token from previous installation.
At least never an 500 internal server error.
HTTP Status 500 internal server error:
52.14.131.139 - - [21/Aug/2025:20:30:17 +0200] "GET /api/index.php/v1/joomlaupdate/healthcheck HTTP/1.1" 500 1696 "-" "Joomla.org Automated Updates Server" [245297]
52.14.131.139 - - [21/Aug/2025:20:45:13 +0200] "GET /api/index.php/v1/joomlaupdate/healthcheck HTTP/1.1" 500 1696 "-" "Joomla.org Automated Updates Server" [40852]
52.14.131.139 - - [21/Aug/2025:21:00:15 +0200] "GET /api/index.php/v1/joomlaupdate/healthcheck HTTP/1.1" 500 1696 "-" "Joomla.org Automated Updates Server" [41797]
SELinux CentOS Stream 9, PHP 8.4.11, Apache 2.4.62
For the 500 there are no entries found in Joomla logs (even with 'Log Almost Everything' and 'Debug System' enabled) and not in PHP error log.
This test was supposed to verify the fix for 45934. Therefore, on 21 Aug 2025, 21:15 CEST the Automated Updates was enabled, the instance was automatically updated to 5.4.113 and after that there was successfully only the HTTP status code 200 OK for joomlaupdate/healthcheck
every 75 minutes.
Labels |
Added:
No Code Attached Yet
|
So, from my perspective: expected behavor.
Doesn’t a 500 error always mean something went wrong on the server and it needs to be fixed?
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-08-22 15:45:38 |
Closed_By | ⇒ | SniperSister |
That's not the error case that we are handling here. The case is a healthcheck call for a site that does not have automated updates enabled at all, which is triggering a runtime exception.