jackaustin
Member
Good morning!
I have been having an issue across a variety of clients running both v15.5 and v16 of 3CX. The management console is locking out accounts even when the correct username and password are entered. What's worse, it is locking out after only a single attempt to log in to the server. On one of these instances, I tried to alleviate this a bit by whitelisting the address but this just made it impossible to unblock the IP in question as it wasn't blacklisted.
At most of the sites/IPs where this has happened, there are no softphones in use and either no phones or no phones that are not properly registered. There are no indications of other failed authentications from the source IP that would account for the lockout after a single attempt (never mind that the correct credentials are being used).
This has happened both with user accounts and the admin account and has occurred in a number of different browsers: Chrome, Brave, and Firefox.
Has this happened to anyone else? Any ideas on how to start troubleshooting this?
I have been having an issue across a variety of clients running both v15.5 and v16 of 3CX. The management console is locking out accounts even when the correct username and password are entered. What's worse, it is locking out after only a single attempt to log in to the server. On one of these instances, I tried to alleviate this a bit by whitelisting the address but this just made it impossible to unblock the IP in question as it wasn't blacklisted.
At most of the sites/IPs where this has happened, there are no softphones in use and either no phones or no phones that are not properly registered. There are no indications of other failed authentications from the source IP that would account for the lockout after a single attempt (never mind that the correct credentials are being used).
This has happened both with user accounts and the admin account and has occurred in a number of different browsers: Chrome, Brave, and Firefox.
Has this happened to anyone else? Any ideas on how to start troubleshooting this?