Bug #76185
closed
Install tool not working when NOT using namebased hosting
0%
Description
When I try to install typo3 8.1 on the default ip based site (Debian nginx, but this applies to other systems too I am sure).
I am always getting:
@Trusted hosts pattern mismatch
The trusted hosts pattern will be configured to allow all header values. This is because your $SERVER_NAME is "_" while your HTTP_HOST is "192.168.102.167". Check the pattern defined in Install Tool -> All configuration -> System -> trustedHostsPattern and adapt it to expected host value(s).
@
I think this should only be displayed when there is already a finished install because I cannot comply with this suggestion.
If I click "Continue anyway, I know what I am doing" all further steps of the wizard are skipped and at least the DB configuration is empty. Front- and backend fail inevitably.
Updated by Joris Willems almost 8 years ago
If I use namebased hosting the install tool does not give the above warning but when I click "System looks good. Continue." it give the same issue with the not configured DB connection and the rest of the wizard skipped.
Updated by Joris Willems almost 8 years ago
Manually adding the db configuration in typo3conf/LocalConfiguration.php is a workaround:
'DB' => [
'Connections' => [
'Default' => [
'charset' => 'utf-8',
'dbname' => 'typo3',
'driver' => 'mysqli',
'host' => 'localhost',
'password' => 'XXXXXXXXXX',
'port' => 3306,
'unix_socket' => '/var/run/mysqld/mysqld.sock',
'user' => 'typo3',
],
],
],
Updated by Wolfgang Wagner almost 8 years ago
Seems to be the same problem? https://forge.typo3.org/issues/76163
Updated by Joris Willems almost 8 years ago
Indeed. The correct title for the bugreport should be "DB connection not configured by install tool in typo3 8.1"
Updated by Joris Willems almost 8 years ago
I am not getting any message about an old Mysql version. The wizard just ends after the first page with typo3 trying to connect with an empty connection.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from New to Closed
That should be already fixed; see #76163, so I am closing it for now.
If you think that this is the wrong decision or experience the issue again then please reopen it or open a new issue with a reference to this one.
Thank you