3cx Admin login - Incorrect Username or Password

[Frank Noone]

I have one client whose admin console randomly won't allow an admin login. I am definitely using the correct Username/Password combo. I do not need to recover the password.

At first, I thought it was just blacklisting us. But I have confirmed that is not the case.

Eventually, I discovered that the autogenerated password had some unusual characters in it and I thought that was causing the issue. Changed the password to where the only special character it contained was an !. That seemed to help at first. but eventually, the issue occurred again.

Now randomly the client calls because of some issue or another and I can't log in to the management console.

If I go in and hard restart the VM completely it will allow me to login.

Again, I have the correct username and password, I am not blacklisted, it doesn't recognize the login.

It's killing me because it's a major interruption to the client for me to go in and have to reboot the entire system.

Any Ideas?

 

[ChrisC_3CX]

Regardless of whether you are sure of the password, did you ever try to use the "Forgot Password" option that appears after the second failed login attempt? If yes, did you actually receive the email but still was unable to login?

Also, are you using a 3CX Failover configuration or is there any chance that the same License Key is being used on a different system and therefore resulting in the DNS record alternating from one IP to the other?

 

[Frank Noone]

Again after rebooting, I was able to log in.

I like your idea on the DNS or the licensing suggestion.

After I rebooted I found that I cannot get the license to renew. So that may be the source of the issue. I've spoken to the client and I am going to build a new instance from scratch and move them over to this weekend.

 

[Lee Cramman]

If you were to troubleshoot then the specific error message shown at login would be useful.

I've had a few issues in the past where the management console service would fall over regularly. It's tended to be a memory issue and throwing a bit of extra memory or swap at the problem cured it.