How to unlock TYPO's Install Tool (/typo3/install.php)? - typo3

After adding an empty text file called 'ENABLE_INSTALL_TOOL" in the 'typo3conf' folder the Install Tool is still locked when I visit hostname/typo3/install.php.
Some background information: I just uploaded all TYPO3 files to a remote host and am trying to get it to display the TYPO3 website. When I logged into the backend I got the following error:
1533822084 TYPO3\CMS\Core\Crypto\PasswordHashing\InvalidPasswordHashException
Configured default hash method
TYPO3\CMS\Core\Crypto\PasswordHashing\Argon2iPasswordHash is not available. If the instance has just been upgraded, please log in to
the standalone install tool at typo3/install.php to fix this. Follow
the wiki link for more details.
This error referred to this wiki page: https://wiki.typo3.org/Exception/CMS/1533822084
Here it is suggested to:
Call the standalone install tool and log in once. This should detect that argon2i is not available and will configure a different default hash mechanism. A backend login should be possible afterwards.
Which is what I am stuck on since the Install Tool is locked.

When you visit for the first time the address https://yoursite.com/typo3/install.php you should see the following screen:
As you wrote, you have to add a file ENABLE_INSTALL_TOOL (without extension) in the folder /typo3conf/ of your TYPO3 installation; the file can be empty.
After you have done that and refreshed the same page, you should see:
If you have not changed it (which is recommended) , the password should be the same password as the one of the first administrator user you have created during the installation.
If you have changed it and don't remember it, follow the on screen instructions.

Please refer to the official installation guide:
https://docs.typo3.org/m/typo3/guide-installation/master/en-us/QuickInstall/GetAndUnpack/Index.html
You need SSH access to your remote server. FTP or SFTP is not enough because the symlinks are not uploaded.
You need to transfer a zip- or tar.gz-file to the server and unpack it there. Never unpack them on your machine and transfer the files to the server.

I had same issue in Typo3 10 in CentOS 8
The argon2 password hash algorithm only in PHP >= 7.4, not in previous versions in CentOS 8.
In 7.2 / 7.3, argon2 is part of the "standard" extension and is disabled in RH build as libargon2 is not available in RHEL / CentOS
So if you can upgrade to PHP 7.4 it would work.
Alternative method when in PHP 7.3
in LocalConfiguration.php set
'installToolPassword' => '$2y$12$kB0JLQcbADywtxtxjoBoUOrCSk0RHhh/zuKDbFrtAYlr8fUlZ/1Em',
'passwordHashing' => [
'className' => 'TYPO3\\CMS\\Core\\Crypto\\PasswordHashing\\BcryptPasswordHash',
Open install tool ursite/typo3/install.php
password is 'password' (installToolPassword hash value above)
Now create an new admin and use that to login to backend and reset the passwords of other admins

Related

Typo3 CMS throws Error after successful installation

Once I finish installing Typo3 locally on my system using latest xampp on PHP 8 version. Website stops working. Installation gets completed successfully, but once installation is completed, whole website stops working. This is strange. Every time I tried installing latest Typo3 version, 11.5, same issue happens.
Depending on the kind of installation you're likely missing the correct server configuration. Usually it's done by a .htaccess file in the web-root of the installation.
An example .htaccess file, which in many installations never even needs adjustments, is located inside your installation, you just have to copy it in the webroot and rename it to .htaccess. It's located here:
typo3\sysext\install\Resources\Private\FolderStructureTemplateFiles\root-htaccess
In your Screenshot, you are using Port 81 (localhost:81).
I suggest using the default Port 80 and "127.0.0.1" instead of "localhost" (http://127.0.0.1).
Using Port 81 would need changes in your firewall configuration in many cases.
Additionally, your folder structure seems wrong ("/typo3_src-11.5.12/typo3/login?...").
Your backend should be reachable under "/typo3/" or "/typo3/index.php".
If you are using a legacy installation (without composer), the folder /typo3_src-11.5.12/ should be one level above your web server's document root, as stated here:
https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Installation/LegacyInstallation.html

TYPO3 Upgrade Psr Problem vom 10.x to 11.5.8,

I tried to upgrade from 10.x to 11.5.8 and nothing was working anymore. If I try to open the url I recieve the following error message:
Fatal error: Declaration of TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request, TYPO3\CMS\Extbase\Mvc\ResponseInterface $response) must be compatible with TYPO3\CMS\Extbase\Mvc\Controller\ControllerInterface::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request): Psr\Http\Message\ResponseInterface in C:\inetpub\wwwroot\typo3\sysext\extbase\Classes\Mvc\Controller\AbstractController.php on line 243
So the next step was to disable all my extensions.
If I try to open the backend, I recieve the same message as above.
The next step was to use the Install Tool, which was working. But if I try to use some functions like "Upgrade Wizard", "Analyze Database Structure", "
Remove Temporary Assets", ....
But the sys_log and the log files under typo3temp are empty!
And also the firefox degugger is not showing any information.
PHP 7.4.15, no composer installation and chaches all deleted!
What should I do next?
The first error message says that there are Extbase extensions which are not compatible with v11. See https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.0/Breaking-92502-MakeExtbaseHandlePSR7ResponsesOnly.html
For the second error I'd recommend to look into the dev console of your browser. There you might see more information about the error when there is nothing in the logs. (Maybe there is an error when writing log?)
The mentioned file "AbstractController.php" exists only in version 10 and was removed afterwards.
So TYPO3 is using some old files, probably from the file-cache.
You wrote that you use an installation without composer-setup. Those installations have the file-cache saved in typo3temp/var/cache. This folder can be deleted completely and will be rebuilt automatically.
Afterwards TYPO3 version 11 should run and the error-message should never be shown again.
Due to my experiences with updating TYPO3 to a new mayor release, i did the following steps.
Renamed fileadmin dir
Deleted all TYPO3 dirs
Installed the new version of TYPO3
Start TYPO3 from scratch with an new database (use the ID and passwort from the final database, use the right sitename)
Rename the fileadmin dir back to fileadmin
Go into LocalConfiguration.php and switch under DB to the original database
(Maybe) enable 'debug' => true, for BE and FE and set 'displayErrors' => 1, under SYS
Try to start the BE, if failed go to the Install tool.
Start Upgrade Wizard under Upgrade
In the Install tool start the Analyze Database Structure, but be carefull. that you dont't delete any database of your extensions, which not installed yet!
Now the BE should work now and you can upgrade your extensions!
Good Look.

Service 'MongoDB Server' (MongoDB) failed to start

I'm trying to install mongo DB on my local machine with the installer from the official website. But I'm continuously getting this message, can someone help?
I've tried the solution provided here but didn't help.
I suggest doing the following:
Hit Win+R to open up you run.exe then inside of it enter services.msc to open up services. Try locating the service under the name of MongoDB Server and set the Startup Type manually to Automatic - [In addition to that, you could set the username and password manually. If you get a message saying the user was granted login as a service right, try hitting retry on the MSI dialog and see if it starts].
Important:
Don't forget to save and close everything (services.msc) before continuing.
Also very important, you should (must) check your .NET framework version and update it to version 4.5 and above. You could download a software like eg Driver Booster to update all of your drivers and additional components that are outdated.
I ran into the same issue. My problem was the installation location. I was trying to install under C:\MongoDB. I resolved it by installing in the default MongoDb location which is C:\Program Files\MongoDB.
For me this is usually an issue with the configuration file %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
At some time there was an invalid option "snmp" enabled (only valid in enterprise version).
Nowadays, although the installer asks for directories for data and logs it doesn't ALWAYS seem to use these, but defaults to %MONGO_DATA_PATH% or %MONGO_LOG_PATH%, respectively. I don't know where these should be defined, but the server fails at accessing c:\data\db (which doesn't exist). So you have to correct the paths.
I also faced this kind of error. But I just change the Network service to Local system in Log On As tab.
Follow my step-by-step below to resolve it:
Press Win+R, type: services.msc, then looking for MongoDB Server (MongoDB)
Double click on MongoDB Server (MongoDB).
Then it will open properties tab. On that tab click on Log On
After that check two items i.e. Local System account and Allow service to interact with desktop
After that press Apply and OK button. That's it, cheers!!
Open command prompt and copy the following command:-
"C:\Program Files\MongoDB\Server\4.2\bin\mongo.exe"
NOTE: This Tricks is work on my Windows 8.1 PC.
Comment out string with mp: in configuration file: %ProgramFiles%\MongoDB\Server\x.x\bin\mongod.cfg
Like this:
...
#snmp:
#mp:
Click Windows+r, type lusemgr.msc , Go to Groups and double click Administrators, Click Add, Click Advanced and click Find Now. Double click in Network Service (in bottom list) and click OK.
It worked for me.
Installing in the other locations other than the windows directory caused me this error. Reinstalling the setup with the recommended method of "complete" fixed it.
The problem occurs if you have Windows version previous to Windows 10.
Install the following update before installing MongoDB. Click on the link below.
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
It worked for me.
The problem occurs if you have Windows version previous to Windows 7. Install the following update by going to below link you have to download
Windows6.1-KB2999226-x64.msu
#You have to download and install then go to servies.msu and start MongoDB server by Start also go into log on and set to #local machine
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows

TYPO3 8.7.1 backend Login not working

I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.

How do I delete my typo3cms database?

Help is requested to delete a database I have created in TYPO3 setup.
I have installed XAMPP in Ubuntu 16.04 and configured it correctly and it runs. Now I was in the process of configuring TYPO3 in XAMPP using this very good guide.
After creating the "typo3cms" database, the next stage asked for a user name and password. I think I was supposed to put in my Ubuntu username and password, but erroneously I put in a new username and password and got the error of not being able to connect to my database.
I tried to go back to the previous stage of creating a database, which I can't because it already exists. But then I cannot go forward anymore. I have no idea where the database resides so that I can delete it and recreate it. I have tried uninstalling typo3 and reinstalling it. I have tried to google the problem without success.
Short of purging xampp completely and starting from scratch, is there a way I can delete the typo3cms database I have created?
It sounds like you are so early in the install process that you can start over (by removing all files and doing the install from the beginning).
Alternatively you should be able to remove typo3conf/LocalConfiguration.php and make sure that FIRST_INSTALL exists in document root (this is an empty file used to indicate that TYPO3 is doing the first install, it gets removed after - and you can use touch FIRST_INSTALL in terminal to create the file). Or if you prefer a completely manual approach, manually edit the typo3conf/LocalConfiguration.php file to correct or remove the database credentials and then resume the install.