FAQ

1. Conflicts with Existing Ports

Port conflicts are one of the most common issues encountered during software installation. SliverWorkspace uses the following ports:

Port	Notes
80	Nginx Web service
443	Nginx Web service
8443	Java backend service
10443	WebSocket persistent connection
5433	postgreSQL database service (changed to 5433 in version 2.7 to reduce the probability of conflicts with databases already on the server)

A conflict with ports already in use on the server causes Docker containers to fail to start.

# 1. View the list of ports already in use on the server
$ netstat -tuln

# 2. Check whether the Docker containers started successfully; switch to the installation directory
$ cd ${install_dir}

# 3. If you suspect a port conflict between the installer and existing services on the server, run the following command in the installation directory to stop the services
$ docker-compose down

# 4. Check the running status of the Docker containers
$ docker-compose ps

# 5. If the output looks like the following, the services started normally. If the State column shows Exited, the container failed to start
          Name                        Command               State                    Ports                  
------------------------------------------------------------------------------------------------------------
sliverworkspace-backend    /bin/bash -c  echo 'Asia/S ...   Up                                              
sliverworkspace-database   docker-entrypoint.sh postgres    Up      0.0.0.0:5433->5432/tcp,:::5433->5432/tcp
sliverworkspace-frontend   nginx -g daemon off;             Up                                              
sliverworkspace-server     /bin/bash -c echo root:${P ...   Up

2. Insufficient Available Memory

Q: Insufficient available memory is also a common cause of software startup failure.

A: The recommended minimum memory configuration is 10 GB. This is especially important when installing the software on a VMware virtual machine — the memory should be configured to at least 10 GB. A lower value may cause the backend application container to fail to start.

3. Abnormal Display of Server Monitoring Charts

Q: After login, the server performance monitoring charts on the home page (dashboard) do not display:

A: If the server login information (username, password, and key) is correct and system authentication passes, the issue may be caused by the language settings of the graphical interface. Log in to the server via an SSH terminal and run free -k to check whether the output is displayed in English. The language of the system's graphical environment (if installed) must be set to English (character set UTF-8, which can be en_US.UTF-8 or zh_CN.UTF_8).