Node latency is normal but connection times out: troubleshooting from TCP to Reality
The delay number only represents the success of a certain kind of detection, but does not mean that the complete proxy handshake and actual business traffic must be successful.
Before you start
Operation steps
- 01
Change node confirmation range
Test at least two nodes in different regions. A single node failure is usually a node-side problem, while a total failure is more likely to be a local machine, account, or current network problem.
- 02
Synchronize system time
Time skew affects secure handshakes such as TLS. Turn on the system automatic time and automatic time zone and try again.
- 03
Update subscription
Old configurations may continue to display nodes after adjustments to server parameters, but connections cannot be completed. Manually update the configuration and try again.
- 04
Distinguish between TCP and protocol handshakes
Successful port detection can only prove that TCP is reachable; Reality or TLS may still fail in subsequent handshakes. Preserve the specific error text in the client.
- 05
Change access network
Switch once between Wi-Fi and mobile hotspot to determine whether the current operator, router or office network has restrictions.
After completion, check like this
- Two regions were tested
- System time is accurate
- Subscription updated
- Full error type logged but no credentials exposed
FAQ
What should I do if I see connect error: EOF?
First update the subscription and change the node. If multiple users appear on the same node at the same time, operation and maintenance should check the Reality handshake target and server logs.
Does successful nc or port detection mean that the node is normal?
No; it only proves that the TCP port can establish a connection.