Update disallows login

Yes, there was a potential conflict with the Session changes in the Brute-Force Protection released in version 4.23.56 on Saturday. That is why I released another update on Sunday, version 4.23.57 should solve this issue for you.

Please download the latest version and let me know if you have any further issues.

4.23.57 is the version I have the issues with. I just manually disabled the Brute Force Protection by commenting out the code for now on a few sites where clients actually login semi-frequently. Others I am sure won’t even attempt a login for a week or so and I suspect you may fix it by then.

Thanks

Thanks for the followup. I would like to fix this today if possible but I may need more help from you to narrow down the cause. As mentioned I had thought that this issue was already fixed in my latest release, as all those who reported the issue with 4.23.56 also confirmed that it was fixed in 4.23.57, but if you are still having a similar issue then I need to take another look.

Is there any can provide me with more details to help me narrow down the cause? Perhaps this issue is only present on a subset of the sites on your server and not all, or maybe there is another reason the sessions suddenly stopped working on your server (like a read-only filesystem in the the temp directory where session files are written, or the temp partition is out of free space). Can you please contact me directly with any details that might help me troubleshoot this issue?

eli AT gotmls DOT net

This was all my fault, Eli remains undefeated! ??