Closed FallynB closed 1 year ago
This should be fixed now.
The underlying problem is that the lambda server only allows your user account to be logged in with 4 sessions at the same time. Probably you had previously been logged in and were logged off abnormally (possibly due to internet issues). These abnormal logoffs remain connected for about 5 minutes after the disconnection, and then they get removed automatically.
In the future if this happens, just waiting 5 minutes should resolve the issue.
Hi, unfortunately I'm having the same issue. I've waited five minutes and then tried logging in again a few times, but keep getting this message:
Too many logins for 'Charles.Hatcher.25'.
Last login: Tue Feb 7 19:17:02 2023 from 134.173.248.5
Connection to 134.173.191.241 closed.
Could this be a variation of the above issue? Any help would be much appreciated!
Update –– I got in after about two hours. Not sure what changed, but I'm just posting the fact that I eventually got in in case it's helpful for debugging.
Hi, I am also running into the same issue with too many logins (I already waited some time) and am still getting this message below. Is there any way to resolve this issue quicker? Thanks!
Derik.Suria.23@134.173.191.241's password:
Too many logins for 'Derik.Suria.23'.
Last login: Thu Feb 9 20:55:05 2023 from 75.83.92.245
Connection to 134.173.191.241 closed.
Update: I was able to login after about 2 hours as well- not sure why it took so long.
Hi Mike,
I am getting the error below when I go to login to the lambda server. What would be the correct way to fix this?