No Response During Login from a Browser

Symptom

When you enter https://server_IP_address:port_number (for example, https://xx.xx.xx.xx:8086) in the address box of a browser, you are redirected to a wrong page or there is no response to login operations.

Possible Causes

Port 8086 is occupied by another tool and cannot be allocated.

Troubleshooting Procedure

Configure the HTTPS port number and log in again.

The default HTTPS port number is 8086.

Use an SSH tool to remotely log in to the OS CLI.
Stop the following services:
```
systemctl stop devkit_nginx
systemctl stop java_perf
```
- Before changing the IP address and port number, you must stop the Kunpeng DevKit. If the Java Profiler is not installed, you do not need to stop the java_perf service.
- If the tool is installed in a container, you can run docker_service.sh to stop the service, such as devkit_nginx. (Replace the example directory /opt with the actual tool installation directory.)
  bash /opt/DevKit/tools/docker_service.sh stop devkit_nginx

Check for port conflicts.

Run the following command to access the tools directory (/opt is the tool installation directory. Replace it with the actual directory.):
1
cd /opt/DevKit/tools/

Check for port conflicts.

1	sh change_ip_port.sh

After the automatic modification is complete, the following port information is displayed. xxxx is the new port number, and xx.xx.xx.xx is the IP address of the running environment.

  Changing the IP address or port requires service restart. In the multi-node scenario, this will cause the remote node to be unavailable and you need to add the remote node again on the Agent Management page. Are you sure you want to continue? [y/N]: y
Please enter install port. (The default install port is 8086):xxxx
...
Web console is now running, go to: https://xx.xx.xx.xx:xxxx

After the script is successfully run, the Nginx service automatically starts.

Parent topic: FAQs