Infrastructure

The previous post covered deploying Xray REALITY on the server side. This one focuses specifically on client configuration—once you’ve collected the usernames, server addresses, public keys and other info for various platforms, here’s how to configure them in different clients. You’ll need to prepare the following information (obtained from the server configuration): Parameter Description Server Address VPS public IP Port Port the server listens on (port 443 recommended) UUID Client ID configured on the server Public Key Public key generated by xray x25519 Short ID One of the shortIds configured on the server SNI serverNames configured on the server (e.g., www.apple.com) mihomo (Clash Meta) mihomo natively supports REALITY. Add the configuration to the proxies: section: ...

Over the past year, I’ve run into a recurring problem with AI tools: airport shared node IPs get flagged by AI platforms, triggering verification requests, feature restrictions, or even account bans. The root cause is simple—these IPs have been used by too many people, and the platform’s risk control system treats them as “abnormal traffic.” The solution: use residential IPs as your exit point. Residential IPs come from real home broadband connections, so to platforms they look like ordinary users—much higher approval rates. ...

Hysteria2 is based on the QUIC protocol (UDP), and is theoretically much faster than TCP-based protocols in high-latency, high-packet-loss networks. However, many people find speeds are mediocre after deployment—usually because bandwidth parameters aren’t configured correctly or the right congestion control algorithm isn’t selected. This article focuses on tuning. It assumes you’ve already got the basic deployment working (see Hysteria2 Setup Guide) and now want to maximize your speeds. ...

AI services like Claude, ChatGPT, and Perplexity are highly sensitive to outbound IP quality. If you route through a standard datacenter VPS proxy, you’ll often hit: Login verification codes Identity re-verification requests Restricted features (Claude Projects, ChatGPT Plus capabilities, etc.) Silent request throttling The reason: these services’ fraud detection identifies IP origins. Datacenter IPs carry the known “proxy traffic” fingerprint; residential IPs don’t. ...

Running paid VPS like DMIT for proxy nodes is stable but costly. What many don’t know is that Cloudflare Workers comes with 100,000 free requests daily—enough to run a completely free VLESS node as a backup or alternative. It’s worth deploying one for everyone. This guide uses the open-source project edgetunnel, deployable in under 10 minutes. Overview Cloudflare Workers is a JavaScript runtime at CF’s edge nodes. edgetunnel implements the VLESS protocol in a Worker, routing traffic through CF’s CDN network to bypass direct IP identification. ...

Running quant strategies and proxy nodes without monitoring is extremely risky. Out-of-memory crashes at 3 AM, disks filling up, strategies crashing—without alerts, you might not notice for hours. This guide builds a complete monitoring stack from scratch: Node Exporter collects metrics on each monitored machine, Prometheus aggregates and stores them, Grafana visualizes the data, and Telegram delivers alerts. Architecture Monitored VPS (N machines) Central Monitoring VPS (1 machine) ┌──────────────┐ ┌─────────────────────┐ │ Node Exporter│ ──9100──→ │ Prometheus │ │ Node Exporter│ ──9100──→ │ (collect & store) │ │ Node Exporter│ ──9100──→ │ Grafana │ └──────────────┘ │ (visualize) │ │ Alertmanager │ │ (alerts) │ └─────────────────────┘ The approach: dedicate a small VPS (1 core, 1 GB RAM is plenty) as the monitoring hub; install Node Exporter on all other machines to expose metrics. ...

Many people think having a VPS proxy node is enough—it’s not. VPS IPs come from data centers, and many platforms impose extra restrictions on data center IPs. OpenAI won’t let you register with a data center IP, some platforms trigger additional verification, and accounts get restricted for “suspicious login”… These scenarios require residential IPs. IPRoyal is a residential IP service I’ve been using long-term. This article clarifies when you need residential IPs and how to use them. ...

DMIT is my primary VPS provider, and I’ve been using it for over a year. Its Hong Kong and US nodes offer the best connection speeds and stability I’ve experienced, with a low IP block rate. Many people see DMIT’s English interface and don’t know how to purchase. This guide walks you through the entire process. Why Choose DMIT When picking a VPS, three things matter most: latency, stability, and IP quality. ...

The previous article on multi-gateway home network architecture covered the overall design but didn’t dive into the details of writing rules. This post focuses specifically on Mihomo’s traffic splitting rules, breaking down everything from syntax basics to practical configuration templates. Basic Concepts of Rules Mihomo controls traffic splitting through the rules field. Each rule follows this format: rule-type,match-value,proxy-group For example: rules: - DOMAIN-SUFFIX,google.com,Proxy - IP-CIDR,192.168.0.0/16,DIRECT - GEOIP,CN,DIRECT - MATCH,Proxy # fallback rule — matches all remaining traffic Rules are matched in order — the first rule that matches is executed, and subsequent rules are skipped. Order is critical. ...

Hysteria2 is a proxy tool based on the QUIC protocol (UDP) that significantly outperforms TCP in high-loss and high-latency networks. It complements VLESS+XTLS-Reality: use Hysteria2 when TCP is throttled, and VLESS+Reality when UDP is blocked—deploying both protocols together is currently the most stable approach. Why Choose Hysteria2 Core advantages: QUIC/UDP-based, maintains good speed even in high-loss networks Built-in bandwidth obfuscation makes traffic patterns harder to identify precisely Simple configuration, lighter weight than Xray Native support in mihomo (Clash Meta) Use cases: ...

Xray’s VLESS+XTLS-Reality is widely recognized as the most robust protocol combination for anti-censorship. Its core principle is disguising traffic as a normal TLS handshake, making it difficult for the GFW to identify proxy traffic through signature detection. This guide walks you through deploying a fully functional setup from scratch. Prerequisites An overseas VPS (I recommend DMIT Hong Kong or US nodes for excellent routing quality) VPS OS: Ubuntu 22.04+ Local client: mihomo (formerly Clash Meta) Server Deployment Install Xray bash -c "$(curl -L https://github.com/XTLS/Xray-install/raw/main/install-release.sh)" @ install Generate XTLS-Reality Keys xray x25519 Output: ...

IP blocks are a common issue for proxy nodes, and I’ve dealt with it many times. This article outlines the complete troubleshooting process. Step 1: Confirm If It’s an IP Block or Something Else When you can’t connect to a node, first rule out non-blocking causes: # Test IP connectivity from mainland China (use mobile hotspot to rule out local network issues) ping your_VPS_IP # Test if the port is open nc -z -w5 your_VPS_IP 443 && echo "open" || echo "blocked" Common confusion cases: ...