Thank you very much. I was looking for things named ban..._xxxx. My mistake.
With this information I updated the database config directly:
login_threshold : set to 99
login_expiry : set to 1
purge_expired_bans : already set to 1 (I assume this meas "Yes, do purge expired bans", but they don't appear to be purging any longer. They did earlier, but apparently no longer.)
Note: Initial setting of login_threshold to 998 caused an error
--
-- From database.log.php:
---
Jan 02, 2020 at 09:12 PM - While executing query 'INSERT INTO cpg16xbanned (ip_addr, expiry, brute_force) VALUES ('10.0.0.132', '2020-01-02 21:13:47', 998)' in login.php on line 91 the following error was encountered:
1264 : Out of range value for column 'brute_force' at row 1
---
Apparently the documented maximum value of 999 is not actually supported. Reverted to value of 99, which worked.
After updating these settings it was also necessary to manually delete the prior ban record from table cpg16xbanned.
The expiry time had already expired, but it failed to be purged after several hours.
I attempted to log in as "user" with the correct password, but login failed, and I found a new ban record in table cpg16xbanned. This new record did show the correct brute_force parameter as "99", which matches the parameter value I set. Regardless, however, an immediate ban was still applied. After waiting a few minutes I checked, and this ban record, although expired, was still present. I may not have purge_expired_bans set correctly.
I am stumped, and am open to suggestions for how to proceed from here. I must be overlooking something because every login attempt now results in being banned, even with the new thresholds. Coppermine does not tell me I have been banned, though. It just says "Login failed. Try again." This is different behavior from what I saw earlier, when it actually did say "You have been banned from this site". Seems like something very odd is going on.
Hope someone canprovide some insight on this.
Thanks in advance