#94465Backend / Frontend inaccessible after installation
Description
Composer based installation of TYPO3 11.2.0 on a Windows 10 System with XAMPP.
Webserver
- Apache
- MySQL
At the end of the install tool neither backend nor frontend are accessible.
After login the error “Page not Found – The Page did not exist or was inaccessible. Reason: No site configuration found.” is shown.
The only accessible part is the Admin tool via “ENABLE_INSTALL_TOOL”.
Can be reproduced in my environment.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 13
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2021-08-10T17:34:27+00:00" > 08/10/21, 17:34 </span>
-
Stefan Hepp commented and changed Tags
11.2, Install Tool, Backend11.2, 11.3.3, Install Tool, Backend <span data-processor="relativetime" data-value="2021-08-25T11:42:06+00:00" > 08/25/21, 11:42 </span>No, still the same error.
It doesn’t matter if I use the Install Tool or console installer.
Always leads to the “Page Not Found….. Reason: No site configuration found.” -
Benni Mack changed target version <span data-processor="relativetime" data-value="2021-09-07T07:44:17+00:00" > 09/07/21, 07:44 </span>
-
Oliver Kurth commented <span data-processor="relativetime" data-value="2021-09-09T15:52:07+00:00" > 09/09/21, 15:52 </span>
The same problem is in MAMP on Windows 10
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2021-10-07T08:16:32+00:00" > 10/07/21, 08:16 </span>
-
Benni Mack commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2021-10-13T10:57:01+00:00" > 10/13/21, 10:57 </span>Can you check if the same happens now in TYPO3 v11.5.1 LTS?
-
Florian Seirer commented <span data-processor="relativetime" data-value="2022-03-22T15:54:12+00:00" > 03/22/22, 15:54 </span>
Just had the same error with TYPO3 11.5.8 on a fresh XAMPP installation:
/typo3/index.php works and /typo3/install.php works, but I can’t log into the backend.Instead I get a 404 error from /typo3/login?loginProvider=1433416747.
The frontend error makes sense though, because TYPO3 11 was just installed, and there are no pages or site config yet.
The frontends and backends of TYPO3 9 and 10 installations on the same XAMPP work fine.
I might also add that all three TYPO3 installations were done using the “classic way”, and not with composer.
-
Riccardo De Contardi changed status
Needs FeedbackNew <span data-processor="relativetime" data-value="2022-09-24T14:36:03+00:00" > 09/24/22, 14:36 </span> -
Florian Seirer commented <span data-processor="relativetime" data-value="2023-01-25T10:27:24+00:00" > 01/25/23, 10:27 </span>
Still the same error on 11.5.22, but only if you select “Take me straight to the backend” during the installation process (step 5/5).
If you select “Create empty starting page” or “Yes, download the list of distributions” instead, everything works.
In /typo3/sysext/install/Classes/Controller/InstallerController.php “case ‘donothing’” is missing in executeDefaultConfigurationAction(), and so $nextStepUrl isn’t defined in this case. Not sure if this would make a difference…
-
Jörn Wagner commented <span data-processor="relativetime" data-value="2023-03-06T10:16:25+00:00" > 03/06/23, 10:16 </span>
Dominik Weber wrote in #note-4:
> Here’s the solution: https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/11.0/Breaking-93048-BackendURLRewrites.htmlHow do I do this with the Symfony Local Web Server, which we use on local machines to develop?
Setting up the first v11 project and I can’t get past the FIRST_INSTALL…
Edit: It does work with the PHP Development Server.
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-02-07T08:46:38+00:00" > 02/07/26, 08:46 </span>Hey! A lot of time has passed by and in the meantime 12, 13 has been released and a lot of effort has been put into improving the installation process. Therefore closing this issue.
If still valid, feel free to contact me on slack
I’ve got the same issue. Were you able to resolve this?
Edit: I’m using 11.3.3