#94470Site Error Pages
Description
I work with an installation where 64 Domains are hosted.
The defined Error-Pages are shown for the first 49 Domains and for further Domains not anymore.
For the domains 50+ the general error-page is shown “Oops an error occured”.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 4
-
David Bruchmann commented and changed attached clipboard-202107021852-e1zpe.png <span data-processor="relativetime" data-value="2021-07-02T11:49:09+00:00" > 07/02/21, 11:49 </span>
-
Stefan Bürk commented <span data-processor="relativetime" data-value="2021-07-14T20:58:33+00:00" > 07/14/21, 20:58 </span>
Some questions:
- Have you checked, that the configured (external) 404 pages are accessible directly for the domains 50+ ? (Show content from page -> external url or internal ?)
- Have you thought of to use a typo3 page as 404/error page and use it directly instead of requesting it with a subrequest ?
- The errorpage is something with an folder .. is it a “typo3 page?” then directly use the t3://page thing instead of external request
- Are the domains protected by basic auth ? ==> add a working auth to the error page url: http://<user>:<pass>@www.domain.tld/404-not-found</pass></user>
- Are the domains http or https ? if https, in your log it stated http .. try with https setup directly. Maybe it conflicts with an redirect ??
- Can you check what is mainly different in the 50 configuration to thr 50+ configurations ?
- The last one evenually resulted in a request loop if it goes to typo3 -> errorhandler -> subrequest typo3 -> errorhandler -> subrequest typo3 -.— and reached a timeout
Setting something up to “test/verify” this is a task for itself ;)
-
David Bruchmann commented <span data-processor="relativetime" data-value="2021-07-28T16:24:56+00:00" > 07/28/21, 16:24 </span>
Hi Stefan,
sorry for not answering earlier.
quote your questions and answer below each:> Have you checked, that the configured (external) 404 pages are accessible directly for the domains 50+ ? (Show content from page -> external url or internal ?)
yes, the pages could be called directly as long as I never implemented an own error-handler.
This applies to all domains.> Have you thought of to use a typo3 page as 404/error page and use it directly instead of requesting it with a subrequest ?
I never made subrequests but used the site-configurations to configure the error-pages.> The errorpage is something with an folder .. is it a “typo3 page?” then directly use the t3://page thing instead of external request
The site-config is writing error pages like this, it was in use.
> Are the domains protected by basic auth ? ==> add a working auth to the error page url: http://<user>:<pass>@www.domain.tld/404-not-found
All domains are and have been public available.
> Are the domains http or https ? if https, in your log it stated http .. try with https setup directly. Maybe it conflicts with an redirect ??
Everything is configured with https.
In frontend there haven’t been any indications that http versus https caused problems.> Can you check what is mainly different in the <50 configuration to thr 50+ configurations ?
The differences are slightly only and mainly related to content only.
All domains use the same default-setup.> The last one evenually resulted in a request loop if it goes to typo3 > errorhandler
> subrequest typo3 -> errorhandler -> subrequest typo3 -.and reached a timeoutI never understood what happened in detail and even remarked that curl-requests to the error-pages have been made.
Concernig “subrequest” I’m not sure if I understand what you mean exactly, perhaps you can elaborate.> Setting something up to “test/verify” this is a task for itself
Sure, that’s some work, is there in ddev some option perhaps to provide an installation similar like a composer file allows installation anywhere?
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-09-07T20:20:15+00:00" > 09/07/26, 20:20 </span>This should be obsolete since TYPO3 v11.4.
In v10 the PageContentErrorHandler always fetched the error page through a real
HTTP request via cURL against the very same server. Every 404 therefore occupied
one PHP worker that blocked waiting for a second worker to render the error page.
That also explains the “works for the first 49 domains” boundary: there is no
per-domain limit anywhere in site handling – this is simply the FPM pool size
(pm.max_children). Once that many 404s are in flight, no worker is left to serve
the error page and everything runs into the 30s cURL timeout, which is exactly
the “cURL error 28” in the report.This was changed with #94402 (“Fetch error pages via subrequests instead of
HTTP”, commit 448a50c97b7, released in v11.4.0). An internal error page – i.e.
a t3://page target, which is what the site configuration module writes – is now
rendered with an in-process subrequest, so no HTTP request and no second worker
are involved. Only a truly external URL still goes through Guzzle, and that path
has a loop guard (“Requested-By: TYPO3 Error Handler”) and degrades gracefully
instead of throwing. Exception code 1544172838 from the report no longer exists
in the core (verified on main).One caveat worth keeping in mind: the error page has to be configured as a page
(t3://page) to take the subrequest path. If an own page is entered as an
absolute external URL, the request still goes out over HTTP and can show the
same behaviour.Since v10 is long EOL and the responsible code is gone, I suggest closing this.
furthermore those entries are added in the log:
clipboard-202107021852-e1zpe.png
Another error looks a bit different: