Issue Bug New Orphaned

#108400Wrong backendlocked modal is shown if TYPO3 backend is not available (httpstatus 403)

Josef Glatz 12/05/25, 06:00 updated 03/04/26, 07:38

Description

Problem/Description

  1. a TYPO3 website where the backend slug (e.g. /typo3) is only available if you are in a specific ip range (e.g. VPN)
  2. keep the backend opened
  3. change your client IP/network/logout from VPN
  4. the webserver (in this case a NGiNX reverse proxy) answer with HTTP status 403
  5. The backendlocked modal is active but informs the editor about “a locked TYPO3 backend for maintenance” – which is wrong in this scenario

!clipboard-202512050656-tr5ev.png!
clipboard-202512050656-9v2rk.png

> The TYPO3 backend is currently locked for maintenance. Leave this browser window open and the backend will automatically become available again once maintenance is complete.

Acceptance Criteria

  • A clear indication that the backend is currently unavailable (status 403) and information that this may be a security precaution would be perfect.
  • It would also be good if an active maintenance lock of the TYPO3 backend could be reliably read from the system.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Wrong backendlocked modal is shown if TYPO3 backend is not available (httpstatus 403) Resolves: #108400 Releases: main