Repository navigation
[fpm-nginx] Critical: Timeout waiting for http://127.0.0.1. #356
Description
After every start of the 8.4-fpm-nginx container, I get:
[03-Sep-2025 11:56:31] NOTICE: fpm is running, pid 2252
[03-Sep-2025 11:56:31] NOTICE: ready to handle connections
127.0.0.1 - - [03/Sep/2025:11:56:36 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:56:41 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:56:46 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:56:51 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:56:56 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:01 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:06 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:11 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:16 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:21 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:26 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
127.0.0.1 - - [03/Sep/2025:11:57:32 +0000] "GET / HTTP/1.1" 503 2540 "-" "shinsenter/phpfpm-nginx-checker" - - - - - - - -
Critical: Timeout waiting for http://127.0.0.1.
Is this an issue?
Activity
shinsenter commentedon Sep 3, 2025
@Commifreak
That is an internal error indicating the web server (Nginx) wasn't ready (health check requests returned HTTP 503) within 60 seconds after the container started.
To disable this feature, set the environment variable
DISABLE_ONLIVE_HOOK=1for the container. When you setDISABLE_ONLIVE_HOOK=1, all scripts for theonlivehook (see Hooks) will also not run.