Debian 9 TYPO3 8.7.20
up vote
0
down vote
favorite
I have had a problem with Debian 9 and Typo3 8.7.20 for two days now and am currently desperate to log in at the Typo3 backend.
The Composer installation of Typo3 was successful up to the point mentioned above. The database tables were all created. I can also log in to the install tool and create a second admin, etc. but the backend does not work. I also repeated the Typo3 installation and always come back to the same result.
In typo3 sys_log there is the following hint:
error: 3
details: Login-attempt from% s (% s) for username '% s' with an empty password!
log_data: a: 3: {i: 0; s: 13: "xxx.xxx.xxx.xxx"; i: 1; s: 0: ""; i: 2; s: 16: "r_admin";}
Unfortunately, I can not find any info with Google
in php.ini I also adjusted the values:
max_execution_time 240
max_input_vars 1500
memory_limit 256M
If you could help me with this problem, I would be very happy. I hope there is a simple solution that I just did not find.
installation typo3 typo3-8.x
add a comment |
up vote
0
down vote
favorite
I have had a problem with Debian 9 and Typo3 8.7.20 for two days now and am currently desperate to log in at the Typo3 backend.
The Composer installation of Typo3 was successful up to the point mentioned above. The database tables were all created. I can also log in to the install tool and create a second admin, etc. but the backend does not work. I also repeated the Typo3 installation and always come back to the same result.
In typo3 sys_log there is the following hint:
error: 3
details: Login-attempt from% s (% s) for username '% s' with an empty password!
log_data: a: 3: {i: 0; s: 13: "xxx.xxx.xxx.xxx"; i: 1; s: 0: ""; i: 2; s: 16: "r_admin";}
Unfortunately, I can not find any info with Google
in php.ini I also adjusted the values:
max_execution_time 240
max_input_vars 1500
memory_limit 256M
If you could help me with this problem, I would be very happy. I hope there is a simple solution that I just did not find.
installation typo3 typo3-8.x
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have had a problem with Debian 9 and Typo3 8.7.20 for two days now and am currently desperate to log in at the Typo3 backend.
The Composer installation of Typo3 was successful up to the point mentioned above. The database tables were all created. I can also log in to the install tool and create a second admin, etc. but the backend does not work. I also repeated the Typo3 installation and always come back to the same result.
In typo3 sys_log there is the following hint:
error: 3
details: Login-attempt from% s (% s) for username '% s' with an empty password!
log_data: a: 3: {i: 0; s: 13: "xxx.xxx.xxx.xxx"; i: 1; s: 0: ""; i: 2; s: 16: "r_admin";}
Unfortunately, I can not find any info with Google
in php.ini I also adjusted the values:
max_execution_time 240
max_input_vars 1500
memory_limit 256M
If you could help me with this problem, I would be very happy. I hope there is a simple solution that I just did not find.
installation typo3 typo3-8.x
I have had a problem with Debian 9 and Typo3 8.7.20 for two days now and am currently desperate to log in at the Typo3 backend.
The Composer installation of Typo3 was successful up to the point mentioned above. The database tables were all created. I can also log in to the install tool and create a second admin, etc. but the backend does not work. I also repeated the Typo3 installation and always come back to the same result.
In typo3 sys_log there is the following hint:
error: 3
details: Login-attempt from% s (% s) for username '% s' with an empty password!
log_data: a: 3: {i: 0; s: 13: "xxx.xxx.xxx.xxx"; i: 1; s: 0: ""; i: 2; s: 16: "r_admin";}
Unfortunately, I can not find any info with Google
in php.ini I also adjusted the values:
max_execution_time 240
max_input_vars 1500
memory_limit 256M
If you could help me with this problem, I would be very happy. I hope there is a simple solution that I just did not find.
installation typo3 typo3-8.x
installation typo3 typo3-8.x
edited Nov 22 at 16:31
Peter Kraume
617313
617313
asked Nov 22 at 11:43
Michael Hellmann
1
1
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07
add a comment |
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Maybe you have [BE][loginSecurityLevel] set to 'rsa' (InstallTool or LocalConfiguration.php) but extension rsaauth is missing? (If your site is on https you can safely set it to 'normal')
Some more hints for debugging:
You can choose 'Debug' under Configuration Presets in the InstallTool
The TYPO3 logs are in typo3temp/var/logs/typo3*.log
Do you get any JavaScript errors from the login page?
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430268%2fdebian-9-typo3-8-7-20%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Maybe you have [BE][loginSecurityLevel] set to 'rsa' (InstallTool or LocalConfiguration.php) but extension rsaauth is missing? (If your site is on https you can safely set it to 'normal')
Some more hints for debugging:
You can choose 'Debug' under Configuration Presets in the InstallTool
The TYPO3 logs are in typo3temp/var/logs/typo3*.log
Do you get any JavaScript errors from the login page?
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
add a comment |
up vote
0
down vote
Maybe you have [BE][loginSecurityLevel] set to 'rsa' (InstallTool or LocalConfiguration.php) but extension rsaauth is missing? (If your site is on https you can safely set it to 'normal')
Some more hints for debugging:
You can choose 'Debug' under Configuration Presets in the InstallTool
The TYPO3 logs are in typo3temp/var/logs/typo3*.log
Do you get any JavaScript errors from the login page?
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
add a comment |
up vote
0
down vote
up vote
0
down vote
Maybe you have [BE][loginSecurityLevel] set to 'rsa' (InstallTool or LocalConfiguration.php) but extension rsaauth is missing? (If your site is on https you can safely set it to 'normal')
Some more hints for debugging:
You can choose 'Debug' under Configuration Presets in the InstallTool
The TYPO3 logs are in typo3temp/var/logs/typo3*.log
Do you get any JavaScript errors from the login page?
Maybe you have [BE][loginSecurityLevel] set to 'rsa' (InstallTool or LocalConfiguration.php) but extension rsaauth is missing? (If your site is on https you can safely set it to 'normal')
Some more hints for debugging:
You can choose 'Debug' under Configuration Presets in the InstallTool
The TYPO3 logs are in typo3temp/var/logs/typo3*.log
Do you get any JavaScript errors from the login page?
answered Nov 22 at 14:07
Jonas Eberle
19817
19817
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
add a comment |
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Many thanks for the help! I've found out the following strange behavior now. If I activate the logging I can log in at the backend suddenly. After I disable logging the login on the backend does not work any more. Also the login screen looks different. [BE][loginSecurityLevel] was always set to 'normal'
– Michael Hellmann
Nov 22 at 21:30
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
Could you provide screens of the two different-looking login screens? What doe the php/apache-log and the javascript-console say?
– BastianBalthasarBux
Nov 25 at 10:49
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430268%2fdebian-9-typo3-8-7-20%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe you can add your LocalConfiguration.php (remove any credentials)?
– Jonas Eberle
Nov 22 at 14:08
Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt
– Michael Hellmann
Nov 22 at 17:02
I see a configuration for rsaauth there. Maybe EXT:rsaauth is activated. Not sure if it interferes with loginSecurityLevel=normal. I would either deactivate the extension (via PackageStates.php) or change to loginSecurityLevel=rsa
– Jonas Eberle
Nov 22 at 18:41
I didn't change the values. It was the default values after downloding with composer create-project typo3/cms-base-distribution /usr/local/typo3/typo3_src-8_composer/ ^8
– Michael Hellmann
Nov 22 at 21:52
Now I set both to normal and the EXT:rsaauth was always deactivated. I still can't log in to the backend with this changes.
– Michael Hellmann
Nov 22 at 22:07