Trouble Logging in after upgrade to Providence 2.09

KHSBronx

I just upgraded from Providence 2.0 to 2.09. Running php version 8.3.15 on Ubuntu 20.04.6.

I can't figure out what is going on at login because it seems to be accepting my credentials then immediately attempts to log in again without any credentials. This results in a redirect back to the login page. So, I am unable to get past the login page. Would appreciate any help.

This is the app log showing two login attempts:

2025-07-13 9:10:07 - INFO --> [LOGIN] Successful login for 'Nick'; IP=69.133.200.9; user agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0 (Auth)
2025-07-13 9:10:07 - INFO --> [LOGF] Failed login with redirect for user id '' (/ca2/index.php/Dashboard/Index); IP=68.132.200.6; user agent='Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0' (AUTH)
2025-07-13 9:22:07 - INFO --> [LOGIN] Successful login for 'Nick'; IP=69.133.200.9; user agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0 (Auth)
2025-07-13 9:22:07 - INFO --> [LOGF] Failed login with redirect for user id '' (/ca2/index.php/Dashboard/Index); IP=68.132.200.6; user agent='Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0' (AUTH)

scottcampbell

KHSBronx

For what it's worth, I fixed my system by reverting to the providence/vendor folder in the release zip. I'm on version 2.0.5.Removed the current vendor folder, replaced it with the one in the zip, and restarted services.

I figured out from the logs that login/redirect problem had started a few weeks ago after I tried composer update, but nobody had been logged out or reported problems logging in right away so I didn't notice the problem.

I'm not sure how to help when the distribution causes the problem, but I'll be upgrading fairly cautiously from here.

scottcampbell

I don't know if I can help, but I was having similar problems upgrading from 1.7x to 2.06 a few months ago. Same error sequence:

[LOGIN] Successful login for 'user'
[LOGF] Failed login with redirect

If I recall, after hours of trying things and reading source code on github I traced the the log message to a file that had been slightly modified in 2.06 (I forget which!) so I replaced 2.06 with to 2.05. Worked fine in testing, so I upgraded our production server.

However, the same problem and error message has started happening again even though I haven't upgraded. I did disable the banhammer plugin, but I don't know if those are linked. None of my users (including me) can login on a different browser. I'm a bit terrified that if they logout by accident they'll be stuck.

seth

You've got two different IP addresses in that log. Which is the one you're actually using?

scottcampbell

seth

I'm not the same person who started this thread, but my logs show the same IP:

2025-07-14 13:51:19 - INFO --> [LOGIN] Successful login for 'scampbell'; IP=10.36.248.92; user agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0 (Auth)
2025-07-14 13:51:19 - INFO --> [LOGF] Failed login with redirect for user id '' (/providence/index.php/Dashboard/Index); IP=10.36.248.92; user agent='Mozilla/5.0 (Windows NT 10.0; Win64; x64
; rv:140.0) Gecko/20100101 Firefox/140.0' (AUTH)

Any advice?

mbutel

I can report the same behaviour, can't login, same message in the log:

2025-08-06 18:44:20 - INFO --> [LOGIN] Successful login for 'belen'; IP=157.92.176.11; user agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 (Auth)
2025-08-06 18:44:22 - INFO --> [LOGF] Failed login with redirect for user id '' (/index.php/Dashboard/Index); IP=157.92.176.11; user agent='Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36' (AUTH)
root@wwwprod:/var/www/html/providence/app/log#

mbutel

I can confirm that in my case it is Redis causing the issue. Changing cache to "file" allows for normal login.

seth

What are the max memory and eviction policy settings on your redis install?

mbutel

127.0.0.1:6379> CONFIG GET maxmemory
1) "maxmemory"
2) "0"
127.0.0.1:6379> CONFIG GET maxmemory-policy
1) "maxmemory-policy"
2) "noeviction"
127.0.0.1:6379> CONFIG GET "evict"
1) "lazyfree-lazy-eviction"
2) "no"

seth

If you want to use redis please try setting an eviction policy. It's also a good idea to set an explicit memory allocation.