Skip to main content

​
Single Node Mode

​
Description

Applicable scenarios: Small applications, applications with low data security requirements, can scale to cluster later when volume increases. Advantages: Simple deployment, good performance, supports online scaling. Disadvantages: Cannot provide disaster recovery, requires manual backup.

​
Environment Requirements

  • Linux system (Ubuntu recommended) (Recommended configuration: 2 cores 4GB or 4 cores 8GB)

​
Installation

​
1. Download Executable File

curl -L -o wukongim https://github.com/WuKongIM/WuKongIM/releases/download/latest/wukongim-linux-amd64

​
2. Modify Executable File Permissions

chmod +x wukongim

​
3. Create Configuration File

Create configuration file wk.yaml with the following content: 
mode: "release"
rootDir: "./wukongim_data"
cluster:
  nodeId: 1001 # Node ID
  serverAddr: "xx.xx.xx.xx:11110" # Node internal communication request address
external: # Public network configuration
  ip: "xx.xx.xx.xx" # Node external IP, IP address that clients can access
  • Replace ip with your server’s external IP address
  • Replace xx.xx.xx.xx in serverAddr with your server’s internal IP address

​
4. Start or Stop

# Start (-d means run in background, otherwise run in foreground)
./wukongim --config wk.yaml -d

# Stop
./wukongim stop

​
Port Configuration

PortDescription
5001HTTP API port (only open to internal LAN)
5100TCP port, app clients need to access
5200WebSocket port, web IM clients need to access
5300Management system port
5172Demo port, used for demonstrating WuKongIM communication capabilities
Make sure to open the required ports in your firewall:
# Ubuntu/Debian
sudo ufw allow 5100
sudo ufw allow 5200
sudo ufw allow 5300
sudo ufw allow 5172

# CentOS/RHEL
sudo firewall-cmd --permanent --add-port=5100/tcp
sudo firewall-cmd --permanent --add-port=5200/tcp
sudo firewall-cmd --permanent --add-port=5300/tcp
sudo firewall-cmd --permanent --add-port=5172/tcp
sudo firewall-cmd --reload

​
Verification

Access http://server_ip:5300 to enter the management system. If you can access it normally, the deployment is successful.

​
Additional Verification Steps

  1. Check service status:
# Check if WuKongIM is running
ps aux | grep wukongim

# Check port listening
netstat -tlnp | grep -E ':(5001|5100|5200|5300|5172)'
  1. Test API endpoint:
# Check health status
curl http://localhost:5001/health

# Check version information
curl http://localhost:5001/version
  1. Access demo: Visit http://server_ip:5172 to access the demo interface and test messaging functionality.

​
Service Management

Create a systemd service file for easier management: 
sudo nano /etc/systemd/system/wukongim.service
Add the following content: 
[Unit]
Description=WuKongIM Server
After=network.target

[Service]
Type=forking
User=root
WorkingDirectory=/path/to/wukongim
ExecStart=/path/to/wukongim --config wk.yaml -d
ExecStop=/path/to/wukongim stop
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target
Enable and start the service: 
# Reload systemd
sudo systemctl daemon-reload

# Enable auto-start
sudo systemctl enable wukongim

# Start service
sudo systemctl start wukongim

# Check status
sudo systemctl status wukongim

# View logs
sudo journalctl -u wukongim -f

​
Configuration Optimization

​
Performance Tuning

For production environments, consider the following optimizations: 
mode: "release"
rootDir: "./wukongim_data"
cluster:
  nodeId: 1001
  serverAddr: "xx.xx.xx.xx:11110"
external:
  ip: "xx.xx.xx.xx"
# Performance optimization
logger:
  level: "info"  # Reduce log level in production
  dir: "./logs"
datasource:
  addr: "./wukongim_data"
  shardNum: 32  # Increase shard number for better performance

​
Security Configuration

# Add security settings
security:
  tokenExpire: 3600  # Token expiration time
  maxConnections: 10000  # Maximum connections
  rateLimit: 1000  # Rate limiting

​
Troubleshooting

​
Common Issues

  1. Port already in use:
# Check which process is using the port
sudo lsof -i :5100

# Kill the process if needed
sudo kill -9 <PID>
  1. Permission denied:
# Make sure the executable has proper permissions
chmod +x wukongim

# Check if running as appropriate user
whoami
  1. Configuration file not found:
# Make sure config file exists and is readable
ls -la wk.yaml
cat wk.yaml

​
Log Analysis

# View WuKongIM logs
tail -f ./wukongim_data/logs/wukongim.log

# Check system logs
sudo journalctl -u wukongim -n 50

​
Next Steps

Multi-Node Deployment

Scale to cluster deployment for high availability

Server Configuration

Configure authentication and performance optimization

Monitoring Setup

Set up monitoring and alerting

API Documentation

Start using WuKongIM API