#110030Install Tool - DB Wizard broken on first install
Description
When installing a new new TYPO3 13.4.31, the install wizard opens and I enter the database credentials. The step 2 (MYSQLi, username, password, port, host) succeeds. The step 3 (selecting the database) fails with the error message
> Could not connect to selected database!
> Could not connect to database “db”! Make sure it really exists and your database user has the permissions to select it!
But it still offers the available databases in the select menu.
This does not happen in 13.4.30
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
Files 2
History 10
-
Christian Kuhn changed Related to #110034 <span data-processor="relativetime" data-value="2026-06-10T10:56:22+00:00" > 06/10/26, 10:56 </span>
-
Oliver Hader changed Duplicated by #110031 <span data-processor="relativetime" data-value="2026-06-10T11:22:43+00:00" > 06/10/26, 11:22 </span>
-
Benjamin Franzke commented <span data-processor="relativetime" data-value="2026-06-10T11:50:10+00:00" > 06/10/26, 11:50 </span>
-
Oliver Hader changed
Duplicated by #110031<span data-processor="relativetime" data-value="2026-06-10T12:09:15+00:00" > 06/10/26, 12:09 </span> -
Oliver Hader commented <span data-processor="relativetime" data-value="2026-06-10T12:10:12+00:00" > 06/10/26, 12:10 </span>
Benjamin Franzke wrote in #note-3:
> Hey @ohader,
>
> I’m not 100% sure this is really a duplicate of https://forge.typo3.org/issues/110031 sinceThanks for the analysis. I was under the impression that both a related to “first install”, but I did not investigate further.
-
Benjamin Franzke commented <span data-processor="relativetime" data-value="2026-06-11T07:44:02+00:00" > 06/11/26, 07:44 </span>
Hey Markus,
Thanks for you report. You name 13.4.31 in the text but set version to v14? I guess the latter was a mistake and it actually was meant to be “v13” right?
We could reproduce (and fix) your other report – https://forge.typo3.org/issues/110031 – but this one does not happen for me.
Can you try the process again and try to get more details like a stack trace or some log entries?
Intresting would be:
- Possible errors only visible in Browser inspector, Network tab (like 500er responses to ajax/Fetch requests)
- PHP error log
- typo3temp/var/log/*
Thanks in advance!
-
Markus Kappe changed TYPO3 Version
1413 <span data-processor="relativetime" data-value="2026-06-11T09:05:23+00:00" > 06/11/26, 09:05 </span> -
Markus Kappe commented and changed attached clipboard-202606111137-7eqfo.png attached clipboard-202606111137-z8pno.png <span data-processor="relativetime" data-value="2026-06-11T09:51:48+00:00" > 06/11/26, 09:51 </span>
These steps can reproduce the bug:
ddev config --project-type=typo3 --docroot=public --php-version=8.4 --webserver-type=apache-fpm ddev composer create-project typo3/cms-base-distribution:^13 ddev start touch FIRST_INSTALL rm config/system/additional.php ddev launch(while latest version is still 13.4.31)
It results in:
!{width: 608px}.clipboard-202606111137-7eqfo.png!
.clipboard-202606111137-z8pno.pngThe ajax response (status 200) does not say anything usefull:
{ "success": false, "status": [ { "severity": 2, "title": "Could not connect to selected database!", "message": "Could not connect to database \u0022db\u0022! Make sure it really exists and your database user has the permissions to select it!", "storeInSession": false } ] }Error log (var/log/typo3_*.log)
component="TYPO3.CMS.Core.Error.ErrorHandler": Core: Error handler (BE): PHP Warning: unserialize(): Extra data starting at offset 51736 of 51776 bytes in /var/www/html/vendor/typo3/cms-core/Classes/Serializer/AuthenticatedMessageDeserializer.php line 56
No PHP errors were logged.
As stated before, the procedure works in 13.4.30:sed -i '' 's/\^13\.4/13.4.30/g' composer.json rm composer.lock ddev composer i -
Benjamin Franzke commented and changed status
NewResolved <span data-processor="relativetime" data-value="2026-06-16T06:15:53+00:00" > 06/16/26, 06:15 </span>Hey Markus,
thanks for your answer. We could reproduce this now and that the fix applied for https://forge.typo3.org/issues/110034 solves the problem.
The issue will be resolved with the next TYPO3 (regression) release.Thanks, Benjamin
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:50:53+00:00" > 08/11/26, 08:50 </span>
Hey @ohader,
I’m not 100% sure this is really a duplicate of https://forge.typo3.org/issues/110031 since
To better explain the relation:
https://forge.typo3.org/issues/110031 missed to show the “create FIRST_INSTALL” file info box.
The user then did this anyway (because he knew he has to do that) and then a later step (where encryption key should already be available) failed.
Therefore this might be another bug.