Debian 9 TYPO3 8.7.20












0















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.










share|improve this question

























  • Maybe you can add your LocalConfiguration.php (remove any credentials)?

    – Jonas Eberle
    Nov 22 '18 at 14:08











  • Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

    – Michael Hellmann
    Nov 22 '18 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 '18 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 '18 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 '18 at 22:07
















0















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.










share|improve this question

























  • Maybe you can add your LocalConfiguration.php (remove any credentials)?

    – Jonas Eberle
    Nov 22 '18 at 14:08











  • Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

    – Michael Hellmann
    Nov 22 '18 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 '18 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 '18 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 '18 at 22:07














0












0








0








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.










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 16:31









Peter Kraume

710415




710415










asked Nov 22 '18 at 11:43









Michael HellmannMichael Hellmann

1




1













  • Maybe you can add your LocalConfiguration.php (remove any credentials)?

    – Jonas Eberle
    Nov 22 '18 at 14:08











  • Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

    – Michael Hellmann
    Nov 22 '18 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 '18 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 '18 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 '18 at 22:07



















  • Maybe you can add your LocalConfiguration.php (remove any credentials)?

    – Jonas Eberle
    Nov 22 '18 at 14:08











  • Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

    – Michael Hellmann
    Nov 22 '18 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 '18 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 '18 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 '18 at 22:07

















Maybe you can add your LocalConfiguration.php (remove any credentials)?

– Jonas Eberle
Nov 22 '18 at 14:08





Maybe you can add your LocalConfiguration.php (remove any credentials)?

– Jonas Eberle
Nov 22 '18 at 14:08













Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

– Michael Hellmann
Nov 22 '18 at 17:02





Many thanks! hellmann-online.de/doc/LocalConfiguration.php.txt

– Michael Hellmann
Nov 22 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 at 22:07












1 Answer
1






active

oldest

votes


















0














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?






share|improve this answer
























  • 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 '18 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 '18 at 10:49











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',
autoActivateHeartbeat: false,
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
});


}
});














draft saved

draft discarded


















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









0














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?






share|improve this answer
























  • 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 '18 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 '18 at 10:49
















0














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?






share|improve this answer
























  • 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 '18 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 '18 at 10:49














0












0








0







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?






share|improve this answer













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?







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 '18 at 14:07









Jonas EberleJonas Eberle

19718




19718













  • 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 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 '18 at 10:49


















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

404 Error Contact Form 7 ajax form submitting

How to know if a Active Directory user can login interactively

Refactoring coordinates for Minecraft Pi buildings written in Python