Tabs of regular Flow
Blocks and connections
Gateway cannot be connected directly to the Internet. A CDN must lead to one input node; an input node and a transit node can lead to the next transit or to the exit; rings are not allowed.
The routing condition is set in the communication dialog. For a normal input or transit unit, leave one output for all the rest of the traffic, and set the additional branches with conditions. Balanced alternatives within the pool are described by separately by.
Node tuning
Tap the block twice. Select the physical node or available pool, set up the connection template, transport, security, sniffing and optional settings. Check JSON Preview and validation messages. The available settings depend on the role and template. The supported transports are TCP, WebSocket, gRPC and XHTTP; for XHTTP, use the permissible combinations of mode and parameters from the constructor. REALITY and TLS parameters must correspond to the selected transport and the actual server configuration. For SelfSteal, prepare the domain, DNS, certificate and service itself in the node card. The choice of masking in the draft does not prove its readiness on the server. For TLS and SelfSteal, select the managed node domain. It defines the address, SNI, and certificate paths. When you change the node, the choice is reset; no other binding is accepted by the server. Schemas without an explicit choice use the main domain.First route
1
Add in.
Add the input node and connect it to the Gateway, assign a physical node and set up the connection.
2
Add an exit.
Connect the login to the Internet without a condition. Later, you can add a transit, a pool, or conditional branches.
3
Save and check.
Wait for the canvas to be saved. Open Check and remove the blocking remarks.
4
Look at the plan.
Click “Apply Changes.” The panel will assemble a plan and show you errors, warnings, and confirmations you need.
5
Apply.
Apply the plan viewed, then open Health and check the customer connection.
