SOLVED Anyone seen this one before? Wordpress login "Your account has exceeded the maximum concurrent logins"?

RevivalTech

Active Member
May 6, 2020
27
5
3
United States
cPanel Access Level
Root Administrator
Haven't been able to hunt down the right log to point me to the right adjustment, nor find anything on the net to help thus far.
For some reason I have a feeling that it is something in litespeed (lsws), or whm. I have a faint memory of during initial setup config for lsws coming accross some 'concurrent' setting that may be effecting this, but have not been able to reverse find anything concurrent with lsws to solve issue...

Current my.conf since I have gone down a path recently of thinking perhaps it's mysql concurrent connections related?....

[client-server]
!includedir /etc/my.cnf.d

[mysqld]
log-error = /var/lib/mysql/alderaan.revivaltechmsp.com.err
performance-schema = 0
innodb_buffer_pool_size = 6144000000
innodb_file_per_table = ON
innodb_log_file_size = 1024000000
innodb_flush_log_at_trx_commit = 1
innodb_log_buffer_size = 2048000000
max_allowed_packet = 268435456
max_connections = 1500
max_user_connections = 1500
max_heap_table_size=77M
open_files_limit = 40000
unix_socket = OFF
tmp_table_size=77M
key_buffer_size=64K

1662735380601.png

Rebooting server, changing password, and refreshing wp-config salts to no avail! Different machines do same thing, different internet networks in different locations same thing, and I've made sure to log out of ALL other machines I have ever logged into with this new server / wordpress setup. Suuuuuuuper annoying at this point haha.

Any assistance would be much appreciated! Cheers!
 
Last edited by a moderator:

ffeingol

Well-Known Member
PartnerNOC
Nov 9, 2001
857
368
363
cPanel Access Level
DataCenter Provider
This sounds like a WordPress plugin (like loggedin). There is really no way that LSWS, MySQL etc. would have any idea of application level logins.
 
  • Like
Reactions: cPRex

RevivalTech

Active Member
May 6, 2020
27
5
3
United States
cPanel Access Level
Root Administrator
This sounds like a WordPress plugin (like loggedin). There is really no way that LSWS, MySQL etc. would have any idea of application level logins.
Yeeeaaaaa, that's all I've been able to get in search results even attempting minus operand and whatnot lol. But pretty certain it is not plugged in because I never had limit logins plug-in installed and activated on this WordPress instance, and also have never configured anything on purpose to limit how many logins could be concurrent. Also recently decided that I was educated enough to secure server at server level, and have the activated and removed as well. So then I think of how to audit the system to possibly detect some kind of leftover remnants of word fence but I literally have never had a desire to limit login attempts so then I feel like that might be a wasted Rabbit Hole not worth even starting... ‍smh lol
 

RevivalTech

Active Member
May 6, 2020
27
5
3
United States
cPanel Access Level
Root Administrator
Can you reliably make the issue happen? As in, it's not an intermittent problem that comes and goes? If so, you could always make a ticket with our team if you have root access to the server, and we could take a look.
Yeeeaaaa, it's mostly always, slightly intermittent. Yesterday I was able to login all day, several tabs as needed, then all the sudden later in the day I got the error locking me out. I was preparing my "woohoo" post, thinking that tunings to the my.conf were clearly the fix. Upping max connections / per user to 1500 must have been it! The error message just says concurrent logins and makes you think maybe it's wordpress related, but only thing I find in search is mysql concurrent connections, so I made edits and yay! But unfortunately this is not that post.... haha.

Login will work, then clearly seems the issue is caused because of how I operate with several logged in tabs. Then say I don't have anytime to work on trying to solve it for rest of day, after sometime has passed usually overnight, I can login again. Sometimes it's only one login, on that one tab I can go to few pages, then all the sudden requests login again. Or I get one tab logged in, and logging into ONE more tab will kick the log out too many concurrent connections issue.

Yes yes, it's my server I operate. However, I am no specialist, so I am rather certain it's due to some setting I need to adjust due the choice in special configurations from the ground up of the custom partitioned linode hosted cloudlinux 8 / whm / LSWS / mariadb setup lol. Buuuuut, from my research it SHOULD be the swank setup haha. Have work out a lot of bugs, primarily the craziest was forgetting /home is the main partition for whm user accounts, and having have to figure out how to boot to recovery in linode, mount "external" drive, move files for backup because I found XFS to be suggested for performance but turns out you can shrink. So I backed up, deleted, recreated, and restored. Successfully! haha. But yea that was a nightmare....

Holding off on making ticket thus far, thought I'd start here in the community, hoping you'd show up haha, and see if I can get some assistance in ideas of logs to check on that I haven't learned are places to check for an issue of this type. In goal of having a little more info / testing results before getting to CS to be more helpful and not waste CS time ya know?

Edit: Oh yea, the current idea I just realized was this may have started after turning on OWASP CRS v3.x for ModSec 2.9, and am currnently working one ducating myself on proper tunings for whm/lsws server.... This morning was one where the issue didn't fully reset, as I waws able to login once to one tab, but attempting a 2nd tab caused too amny concurrent issue. Refreshing 1st tabber logged in got logged out and error message. Just turned off OWASP, refresh 1st tab, and logged in.... Excited, logged into 2nd tab, refreshed 1st, logged out again. Refreshed 2nd tab and logged out... Sooooo perhaps not...

Thoughts on OWASP? Any recommendations for tuning, or something else better?

Edit: Man, what the heck could it be if I still get concurrent login block issue EVEN AFTER REBOOTING SERVER?! mind, explodes everytime I've tried this... lol. "ok, if really too many connections/logins, rebooting server, reseting password, refreshing salts, should DEFINITELY cut the connections and allow login, yea that is logical. Yea...." Nope. lol smh...
 
Last edited: