TYPO3 Core

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77131

Patch set 1 for branch 12.1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77152

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77153

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77154

Is this related?

TYPO3 8.7.49 Project:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1476050190: Unable to generate a URL for the named route "install.server-response-check.host" because this route was not found. | TYPO3\CMS\Backend\Routing\Exception\RouteNotFoundException thrown in file /var/www/vhosts/myvhost/dist/typo3/sysext/backend/Classes/Routing/UriBuilder.php in line 73. Requested URL: https://www.my-typo3-8-7-49-project.com/index.php?eID=t3monitoring&secret=123456

I also get this error with "t3monitoring": #1476050190: Unable to generate a URL for the named route "install.server-response-check.host" because this route was not found.

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77131

Patch set 2 for branch 12.1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77152

Had a chat with André Buchmann to analyze this error.

Outcome:

• "Could not resolve host: 1eae60a836.random.example.org" happens because a proxy server produced a 3xx redirect to 1eae60a836.random.example.org/login.php => André's suggestion, which I like: We should not let guzzle follow redirects, but rather mark redirects to the evil host as a fail. (explanation: The evil host header is used in the response)

• The actual issue was that EXT:t3monitoring_client executes the status reports in frontend context, resulting in ABSOLUTE_URL generation without the /typo3/ prefix. https://myhost.com/index.php?route=… instead of "https://myhost.com/typo3/index.php?route=…@

In other words: aha $GLOBALS['TYPO3_REQUEST']->getAttribute('normalizedParams')->getRequestDir() returns / instead of /typo3/ in https://github.com/TYPO3/typo3/blob/v10.4.33/typo3/sysext/backend/Classes/Routing/UriBuilder.php#L148

Not sure whether we can properly fix that without breaking existing assumptions.
But maybe sth. like $GLOBALS['TYPO3_REQUEST']->getAttribute('normalizedParams')->getSiteUrl() . Environment::getBackendPath() would help here (untested).

Patch set 2 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77153

Patch set 2 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77154

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77131

Christian Knauf wrote in #note-9:

I also get this error with "t3monitoring": #1476050190: Unable to generate a URL for the named route "install.server-response-check.host" because this route was not found.

Sounds like some other caching issue. Did you try clearing all caches?

Ah, spotted t3monitoring... seems like this extensions should address it when invoking backend routes from frontend context.

Yes, cleared all caches.

The problem only occurs under TYPO3 8.

I just updated a web to 10.4.33 to test it. The extension t3monitoring works here with version 9.2.0.

In the TYPO3 8 installation it is version 1.0.0.

Maybe that helps.

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77131

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77160

Patch set 2 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 3 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 3 for branch 12.1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77152

Patch set 3 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77153

Patch set 6 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77131

Patch set 4 for branch 12.1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77152

Patch set 4 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77153

Patch set 3 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77154

Patch set 2 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77160

Patch set 3 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77160

Patch set 4 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 5 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 6 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 4 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77160

Patch set 7 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77159

Patch set 5 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/77160

Christian Knauf wrote in #note-17:

Yes, cleared all caches.

The problem only occurs under TYPO3 8.

I just updated a web to 10.4.33 to test it. The extension t3monitoring works here with version 9.2.0.

In the TYPO3 8 installation it is version 1.0.0.

Maybe that helps.

@Christian Knauf The "Unable to generate a URL for the named route "install.server-response-check.host" because this route was not found." Error Occures also on TYPO3 9.5.38 with t3monitoring_client 9.0.3. An extension update 9.2.0 fixes the issue.

I'll now try to find a solution for 8.7.49 & 8.7.50. But this is a different error than the Response code issue fixed here.

André Buchmann wrote in #note-38:

Christian Knauf wrote in #note-17:

I just updated a web to 10.4.33 to test it. The extension t3monitoring works here with version 9.2.0.

In the TYPO3 8 installation it is version 1.0.0.

Maybe that helps.

@Christian Knauf The "Unable to generate a URL for the named route "install.server-response-check.host" because this route was not found." Error Occures also on TYPO3 9.5.38 with t3monitoring_client 9.0.3. An extension update 9.2.0 fixes the issue.

I'll now try to find a solution for 8.7.49 & 8.7.50. But this is a different error than the Response code issue fixed here.

The hint to v9.2.0 of t3monitoring_client leads to this commit https://github.com/georgringer/t3monitoring_client/commit/e408cd8b7804c0d3decdf7e7ce38b408c84ccceb, which shows how backend routing is initialized now.

@Christian Knauf Here is the solution for the t3monitoring_client v1.0.2 (TYPO3 8): https://github.com/georgringer/t3monitoring_client/pull/75

@Oliver Hader Thanks for the regression fix. All our instances are now up-2-date and connected to the T3monitoring again :-D