VMess TLS Websocket Inbound

{
	"type": "vmess",
	"tag": "vmess-tls-ws-in",
	"listen": "::",
	"listen_port": 443,
	"users": [{
		"name": "bitcoinvps.cloud",
		"uuid": "3c1890e2-c768-4247-8a3b-032f6ed13a64",
		"alterId": 0
	}],
	"tls": {
		"enabled": true,
		"server_name": "subdomain.example.com",
		"alpn": [
			"http/1.1"
		],
		"min_version": "1.2",
		"max_version": "1.3",
		"acme": {
			"domain": ["subdomain.example.com"],
			"data_directory": "/etc/sing-box",
			"default_server_name": "",
			"email": "singbox@example.com",
			"provider": "letsencrypt"
		}
	},
	"transport": {
		"type": "ws",
		"path": "/stream",
		"max_early_data": 0,
		"early_data_header_name": "Sec-WebSocket-Protocol"
	}
}
Code language: JSON / JSON with Comments (json)

Download “VMess TLS over Websocket” inbound to your Sing-Box server:

curl https://raw.githubusercontent.com/bitcoinvps/singbox-vpn/main/vmess-tls-ws/server/config.json > /etc/sing-box/config.jsonCode language: Bash (bash)

VMess TLS over Websocket inbound requires a TLS certificate, so we need to create a subdomain.

The subdomain should point to your VPS server’s IP address. You can either use IPv4 or IPv6, depending on the capability of your VPS server.

Replace “subdomain.example.com” with the subdomain you created in the previous step, and replace “singbox@example.com” with the email address you want to use to obtain your certificate.

After testing a successful connection, you can customize other settings as desired, but make sure to match with your client’s VMess TLS over Websocket outbound config.json.

Finally, you can enable singbox service.