Bug #94054
closed
TYPO3 Backend-Login fails if Typo3 is installed in a subdirectory of the domain
Added by Christian Drost almost 4 years ago.
Updated over 2 years ago.
Description
Hi guys,
today i tried the latest TYPO3-11.2 version on my local Debian VM and on our hosted server.
The install and the installtool work fine and i can complete the creation of my project.
But as soon as i try to login to the backend i get an error:
I get redirected to: typo3/login?loginProvider=1433416747
And get this message display:
Page Not Found
The page did not exist or was inaccessible. Reason: No site configuration found.
I don't know if the problem lies within my settings or my TYPO3 installation.
My system variables are the following:
PHP version: 7.4.18
Version: MySQL 5.7.33
Debian Buster: Debian 4.19.181-1 (2021-03-19)
Apache/2.4.38 (Debian)
- Subject changed from TYPO3 Backend-Login fails on Debian to TYPO3 Backend-Login fails on Debian + idem on SuSE
Got the completely same problem with 11.3.0
My problem was that i called the TYPO3 path via ip/folder (192.168.0.1/mytypo3.t3) and the solution is that is has to be a domain to the projectfolder now (example.com points directly to mytypo3.t3).
I modified a domain in my local host file and redirected that domain to the folder on my vm, for our hosted server i dedicated a subdomain and both projects are now working as intended.
on the same server opensuse 15.3 switching between Typo3 10.4.16 and 11.3.1 by only changing the typo3_src link
typo3/install OK
typo3 FE OK
typo3 BE error as above only on 11.3.1 even with a new administrative user created by 11.3.1 install admin tool.
Same here.
TYPO3 11.2.0 and TYPO3 11.3.1 tested
BE-Login works with DDEV
But not at my provider (nginx with PHP 7.4 and 8.0 tested)
Installtool works
same here. In the rewritecond in the .htaccess file, removing the ^character before typo3 works, but that would probably mean that if you have a page called typo3 somewhere in the pagetree, it would try to route it to the backend...
Not sure if there is a way to make it work for subdirectories without manual configuration. Tried to use the cwd variable, but apparently thats not possible in the CondPattern part..
For now i just added the subdirectory path to the Cond Pattern
so instead of
RewriteCond %{REQUEST_URI} ^/typo3/.$*
you can write
RewriteCond %{REQUEST_URI} ^/SUBDIR/typo3/.$*
- Subject changed from TYPO3 Backend-Login fails on Debian + idem on SuSE to TYPO3 Backend-Login fails if Typo3 is installed in a subdirectory of the domain
Same here with TYPO3 11.3.3
I don't installed it in a subdirectory. Provider: Timmehosting
Locale in DDEV it works fine.
It would be good to know, where the URL .../typo3/login?loginProvider=1433416747 come from.
The file or folder '/typo3/login' does not exist. Strange.
- Related to Bug #95180: Installation v11 / login backend failed added
Would it be possible to provide the Rewrite also for IIS?
Making a copy from
typo3/sysext/install/Resources/Private/FolderStructureTemplateFiles/root-htaccess
to [WEB-ROOT]/.htaccess
solves the issue without looking in the details.
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF