EN FAQ

中文 | English

Troubleshooting & FAQ

This page summarizes common issues users encounter during the configuration and use of FlowWeaver. For a quick end-to-end check run flowweaver selfcheck (verifies service, listening port, proxied request, system proxy and TUN).

1. Insecure Connection or Certificate Error

• Cause: MITM/QUIC modes are active without the local CA root certificate being trusted.
• Solution:
  1. Click "Certificate Management" -> "Click to Reinstall Certificate".
  2. Restart your browser.

2. Rules Not Taking Effect

• Rule Expiry: Built-in rules may become invalid due to network changes or GFW iterations. You can manually fix them (e.g., by changing modes, SNI, or upstream IPs).
• Check Proxy Status: Ensure the "Start Proxy" button on the main dashboard has been clicked.
• Subscription Priority: When a subscription is active, its rules take priority and hide the built-in rules; check in the connection logs (AutoRouted tag) whether your traffic matches the subscription rules or a custom rule.

3. Subscription Fails to Import or Update?

• Connectivity: Make sure your network can reach the subscription URL (some subscription links themselves require the proxy — enable the proxy first, then update).
• Node test: Run flowweaver sub test to test every node for connectivity; switch away from failing nodes.

4. Do Node Protocols Support UDP?

• Support: Every protocol except http (ss / vmess / vless / trojan / tuic / hysteria2 / wireguard / socks5) supports UDP, including QUIC / HTTP3.
• Tip: If UDP fails, prefer native-UDP protocols like tuic / hysteria2.

5. Cloudflare IP Pool Not Updating

• Connectivity: Check your network's ability to reach Cloudflare edge IPs.
• Manual Reset: Clear the IP pool and restart the optimization (flowweaver cf refresh).

6. Advanced ECH Incompatibility

• Support: Not all websites support ECH. If the connection fails consistently even with optimized IPs, try switching to MITM or TLS-RF mode, or route the site via a subscription node.