This guide is intended for users with some Windows Server experience, and the example is based on Windows Server 2019.
For other Windows versions, adjust the steps according to your actual environment.
If you are not familiar with server administration, use a public server or ask an experienced friend to help with deployment.

​
1. Connect to the Server

Use any of the following remote desktop tools to connect to your Windows server:
  • MSTSC (built-in Windows Remote Desktop)
  • FinalShell
  • Any other remote tool that supports RDP
Once you have logged in successfully, you can continue from the desktop.

​
2. Download the Server

First, right-click the Windows icon in the lower-left corner of the desktop and open Windows PowerShell (Admin).
  • Create the working directory and enter it
cd ([Environment]::GetFolderPath("Desktop"))
mkdir cloudmap
cd cloudmap
dir
  • Download the server package
Two download links are available below. Use the primary address first. If the speed is slow or the link is unavailable, switch to the backup address. 
Invoke-WebRequest -Uri "https://cdn.vpkiki.xyz/CloudMap/Windows.zip" -OutFile ".\Windows.zip" #Primary download link
Invoke-WebRequest -Uri "https://cdn.vpkiki.com/CloudMap/Windows.zip" -OutFile ".\Windows.zip" #Backup download link
download
  • After the download finishes, run the following command to extract the server files:
Expand-Archive -Path "Windows.zip" -DestinationPath "." -Force
unzip
After the steps above are complete, you can start the server.

​
3. Run the Server

Run the following command to start the server: 
.\Server.exe
run
After the command runs, the console will output WebSocket and AccessKey.
  • Copy the WebSocket value into the Address field in the menu
    Note: the WebSocket address shown in the console may use the local IP, such as ws://0.0.0.0:4001/ws.
    You must replace that IP with your server’s public IP before using it.
    For example, if your server’s public IP is 1.1.1.1, then the Address field should be filled with ws://1.1.1.1:4001/ws.
    Otherwise, the client will not connect correctly.
  • Copy the AccessKey value into the Access Key field in the menu

​
4. Congratulations, the Setup Is Complete!!

Click here to see how to connect to a private server from the client
If the client cannot connect to the private server through ws://serverIP:port/ws, check the following:
  1. Configuration: Make sure the server started correctly and is listening on the expected port.
  2. Firewall: Make sure inbound traffic for the required port is allowed on the server firewall.
  3. Network connectivity: Confirm that the client can reach the server and that the connection is not blocked by your network provider or firewall.
  4. Address format: Use the WebSocket address in the following format:
    ws://serverIP:port/ws
    Example:
    ws://1.1.1.1:4001/ws
  5. Access Key: Make sure the access key entered in the menu matches the AccessKey shown by the server.

​
5. Configuration Notes

  • The configuration file is located in Config.json in the server root directory.
  • AccessKey: The access key used by the server. Clients cannot connect without it. If the key is leaked, delete this field and restart the server. A new AccessKey will be generated automatically.
  • IP: The IP address the server listens on. In most cases, no change is needed. Only modify it if your server has multiple IP addresses on one NIC and you want to bind to a specific one.
  • Port: The port used for client connections. Usually no change is needed.
  • WorkerNum: The number of worker threads used by the server. In most cases, leave the default value unchanged.
  • Keep all other fields at their default values.