Virtual Machines


Virtual Machines

Documentation > Products > Virtual Machines > Following Error Occurs at SSH Login: Maximum amount of failed attempts was reached

Following Error Ocurrs at SSH Login: Maximum amount of failed attempts was reached

Note: The configuration and instructions of Linux in this article have been tested on the CentOS 6.5 64-bit operating system. For other types and versions of the operating system, configuration may vary. Please refer to the official documentation for the details about relevant operating systems.

Problem Description:

When logging in to Linux VMs, even if the correct password is entered, it can not be logged in properly. When the problem occurs, it can be logged in through the management terminal or SSH client, or can not be logged in through both modes. At the same time, the following error message appears in the secure log:

Your account is Locked. Maximum amount of failed attempts was reached.

Problem Causes:

Multiple consecutive incorrect input of the password triggers the system PAM authentication module policy restriction, causing the user is locked.


pam_tally2 module can be used for account policy control. Prior to resolving this problem, please perform the following configuration checks:

  1. Log in to the server through SSH client or vnc.

  2. View the corresponding PAM configuration file in the abnormal login mode through cat command. Descriptions as follows:

File Function Description

/etc/pam.d/login Console (vnc) corresponding configuration file

/etc/pam.d/sshd Login corresponding configuration file

/etc/pam.d/system-auth System global configuration file

Note: Each application that enables PAM has a corresponding configuration file with the same name in the /etc/pam.d directory. For example, the configuration file of the login command is /etc/pam.d/login, and specific policiy can be configured in the corresponding configuration file.

  1. Check whether there is following configuration information in the configuration file:

auth required item=user sense=allow file=/etc/ssh/whitelist onerr=fail

Brief description of related parameters:

• item: Set the object type of identity and access management, and optional values ​​include tty|user|rhost|ruser|group|shell.

• sense: Define the control method when the matching item is found in the configuration file. Optional value: allow|deny. Specifically, allow represents the white list mode, and deny represents the black list mode.

• file: Specify the full path name of the configuration file.

• onerr: Define the default return value when the error occurs (eg. the configuration file cannot be opened).

  1. Related policies can improve the security of the server. Users need to decide whether to modify the relevant configuration based on the security and usability.

  2. If you need to modify the relevant policy configuration, it is recommended to perform a file backup before proceeding.

  3. Use the editor such as vi to modify the relevant parameter values as needed, and confirm that the access release for relevant user has been made in the corresponding identity and access management file. Or the entirely delete or comment (add # at the beginning) the entire line configuration, eg.:

#auth required item=user sense=allow file=/etc/ssh/whitelist onerr=fail

  1. Try to log in to the server again.

If your problem still can not solved, please submit open ticket to us.

Update Time:2019-08-28 21:38:32