1. - Check whether the device and client can ping each other.

   Access the Windows Command Prompt and run the ping command to check whether the PC and device are reachable to each other. If the system displays "Request time out", the target device is unreachable.

   Check whether the physical interface that receives ping packets is blocked. If the physical interface is not blocked, check whether the correct gateway address is configured on the device, and whether the device and PC are on the same network segment. If they are on different network segments, run the ip address ip-address { mask | mask-length } command in the interface view to reconfigure the management IP address of the device in the target network segment.

2. - Check whether the login address is correct.

   Check the IP address:port in https://IP address entered in the address box of the browser. If the IP address is incorrect, enter the correct one to log in to the web system.

3. - Check whether the HTTPS service is enabled.

   Run the display this command in the system view to check whether the http secure-server enable configuration exists. If not, the HTTPS service is disabled. Run the http secure-server enable command in the system view to enable the HTTPS service.

4. - Check whether the number of online web users reaches the maximum.

   Run the display http server command in any view to check the maximum number of access users allowed by the web system. Run the display http user command in any view to check the number of online web users. If the number of online web users reaches the maximum number of access users allowed by the web system, you can log in to the device only after other users go offline.

5. - Check whether the IP address is correctly configured.

   Run the display this command in the interface view to check whether the configured IP address is correct. If not, run the ip address ip-address { mask | mask-length } command in the interface view to reconfigure the management IP address of the device.

6. - Check whether the web user is correctly configured.

   Run the display this command in the AAA view to check whether the web user is correctly configured.

   • If the local-user user-name password irreversible-cipher password configuration exists, an AAA user named user-name is configured.
   • If the local-user user-name privilege level level configuration exists, the level of the user user-name is level.
   • If the local-user user-name service-type http configuration exists, the service type of the user user-name is HTTP.
   If any of the preceding configurations does not exist, run the following commands in the AAA view:

   • Run the local-user user-name password irreversible-cipher password command to configure the web user name and password.
   • Run the local-user user-name privilege level level command to set the web user level.
   • Run the local-user user-name service-type http command to set the web user's service type to HTTP.

7. - Check whether access control on web users is configured on the device.

   Run the display this command in the system view to check whether the http acl acl-number configuration exists. If so, record the value of acl-number.

   Run the display acl acl-number command in any view to check whether the web user's client IP address is denied in the ACL. If so, run the undo rule rule-idcommand in the ACL view to delete the deny rule, and run the corresponding command to modify the ACL so that the web user's client IP address is allowed.

In case the management IP address has not been configured please refer to the following table:

Which Interface Is Configured with the Default Management IP Address?