One of the three reasons caused this, and I'm not sure which one was. Therefore, I mentioned all 3 in the hope that this will help others save time.
I initially changed the database user credentials in the .yml options. This does not work because the user in question cannot log in with localhost. However, I used the site to test the connection, which could upset the cookie.
I am having problems accessing the cache folder due to a missing image. So I had to clear the cache and configure some permissions, like you do every time.
Finally, I changed the paths for security.yml
form_login: login_path: /login check_path: /login_check logout: path: /logout
in
form_login: login_path: /account/login check_path: /account/login_check logout: path: /account/logout
Along with related changes in .yml routing
As a result, my already registered user no longer transmitted security credentials, and if I tried to log in using another user / browser, I always came across: "Your session timed out or you turned off cookies"
Numerous hours have been spent after red herring, security checks, login processing, redis, etc.
The answer is below.
source share