No Response During Login from a Browser

Symptom

When you enter https://server_IP_address:port_number (for example, https://x.x.x.x: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.

For Deepin 15.2 (x86), the commands related to the Nginx and Gunicorn services are listed below. The crond service keeps starting the Nginx and Gunicorn processes to ensure that they are immediately restarted in the event of exceptions. As a result, the Nginx and Gunicorn services will not be stopped, and theoretically, the port will not be occupied.

1 2	service nginx_port stop/start/restart/status service gunicorn_framework stop/start/restart/status

Troubleshooting Procedure

Configure the HTTPS port number and log in again.

The default HTTPS port number is 8086.

1. Use an SSH tool to remotely log in to the OS CLI.
2. Stop the service using the stop command in Starting, Stopping, Restarting or Querying Services.
3. Check for port conflicts.
   1. 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/

   2. Run the following command to detect port conflicts and make modifications.

      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.

        1 2	Set the HTTPS port xxxxx Web console is now running, go to: https://xx.xx.xx.xx:8086/#/login

      • After the script is successfully run, the nginx_port service is automatically enabled.
4. Log in to the DevKit WebUI again.