---
title: "TYPO3 Exception 1544172838"
manual: "TYPO3 Exceptions"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3exceptions:typo3-exception-1544172838"
source: "Exceptions/1544172838.rst"
modified: "2026-09-16T07:39:08+00:00"
---

# TYPO3 Exception 1544172838

> [!NOTE]
> Below, the TYPO3 community may have provided additional information or
> solutions for this exception. However, these may or may not apply to your
> particular case. If you can provide more information, you should come back
> here and add your experience and solution steps to this issue once you have
> resolved it.
>
> General TYPO3 troubleshooting tips can be found in the *Troubleshooting*
> section in the menu. You can also ask questions and receive support in the
> [TYPO3 Questions category on talk.typo3.org](https://talk.typo3.org/c/typo3-questions/).
>
> To add your experience, click "Edit on GitHub" above and follow the
> ["Edit on GitHub" workflow](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/EditOnGithub.html#docs-contribute-github-method).
> Also check out
> [our tip on Coding Style and reST](https://docs.typo3.org/permalink/t3exceptions:tip-about-rest-coding-style).

## RuntimeException: Error handler could not fetch error page

-   **::**

    RuntimeException: Error handler could not fetch error page(due to
    no internet connection or protected)

## Migrating from Fluidpages to Flux

If this exception appears while migrating from Fluidpages to Flux,
verify that the corresponding Flux-TS is included.

## 404 error handler set to "Display content from page" (TYPO3 9.x)

```
(1/1) #1544172838 Error handler could not fetch error pageuntimeException
Error handler could not fetch error page
"https://project.localdomain.vm/http-error-404",
reason: cURL error 51: SSL: no alternative certificate subject name
matches target host name 'project.localdomain.vm' (see
https://curl.haxx.se/libcurl/c/libcurl-errors.html)

```

When you have set your 404-error-handler to "Display content from page"
on a development domain, cURL can't call the target page when the
certificate isn't valid.

Solution: test again without SSL or test on a staging system with a
properly installed valid certificate.

## Self signed certificate problem

```
(1/1) #1544172838 RuntimeException  Error handler could not fetch
error page "https://example.de/startseite", reason: cURL error 60:
SSL certificate problem: self signed certificate (see
https://curl.haxx.se/libcurl/c/libcurl-errors.html)

```

You can avoid this exception with $GLOBALS\['TYPO3_CONF_VARS'\]\['HTTP'\]\['verify'\] = false;