If you already have connection details, set Type in Add Server to the specified protocol, then check the address, port, authentication and transport settings one by one. The same port does not mean the same protocol, and a saved entry is not necessarily a working connection. The sections below list the fields for each protocol and explain how to distinguish connection problems from routing issues.
Add Server: Choose the Type Before Entering Details
Before adding a server manually, check whether your details are connection parameters for a single server or a subscription URL that updates a group of entries. Enter individual server details using the steps below. If you have an importable share link or subscription URL, import it in its original format to avoid losing parameters such as the transport path or server name when copying them manually.
Open the Add Server screen
Go to Home, tap “+” in the upper-right corner to open Add Server, then tap Type. Choose the protocol specified in your connection details; don't infer it from the port number or an entry note.
Enter the address and port
Enter the server hostname or IP address and port in their respective fields. If a field asks for a hostname, don't paste an entire URL into it. Don't append a path to the port either.
Check authentication and transport
Enter the password, UUID or key in the fields for the selected Type. If your details also specify TLS, SNI or a WebSocket path, enter each value in its corresponding field. Don't copy parameters from another entry if they aren't provided for this one.
Save and select the entry
After saving, return to Home, select the new entry and enable the connection. Test it against the same known-accessible destination and note whether the result is a timeout, a certificate error or a failure affecting only certain sites.
Authentication, Transport and Fields for Seven Protocols
The table below maps connection details to their corresponding fields; not every parameter has a separate switch in the interface. Some fields appear only after you select a particular transport. In particular, distinguish these three values: the server address determines where to connect, TLS SNI specifies the server name used during the handshake, and the WebSocket Host is the hostname in the HTTP request. If your details provide all three, don't assume they should have the same value.
| Protocol | Required connection fields | Commonly misconfigured parameters |
|---|---|---|
| Shadowsocks | Server address, port, encryption method and password. | The password and encryption method must match the server configuration. If your details specify a plugin and its parameters, don't enter the plugin name in the encryption method field. |
| VMess | Server address, port, UUID, and the specified transport and security settings. | For WebSocket, enter the specified path and Host, if required. For TLS, check SNI separately. Fill in Alter ID only if an older configuration explicitly provides it and the interface has a matching field; don't set it yourself. |
| VLESS | Server address, port, UUID, and the specified transport and security settings. | A UUID in VLESS may look like one used in VMess, but the two protocols aren't interchangeable. VLESS does not provide encryption by itself. Keep the specified security settings for TLS or REALITY, and enter the Flow value exactly as provided. |
| Trojan | Server address, port, password and any TLS parameters required by the server. | The authentication field takes a password, not a UUID. If the server address is an IP and your details provide a separate SNI, keep that domain and leave certificate verification enabled. |
| HTTP / SOCKS5 | Proxy address and port; enter a username and password if the server requires authentication. | HTTP and SOCKS5 use different handshakes. If the server provides a proxy endpoint with TLS, that doesn't mean the proxy connection needs TLS simply because the destination website uses HTTPS. |
| WireGuard | Your private key and tunnel address, peer public key, Endpoint and AllowedIPs; enter a pre-shared key if specified in the configuration. | The tunnel address is not the remote host address. Endpoint points to the peer, while AllowedIPs describes the address ranges routed through that peer; don't enter a server domain there. |
| Hysteria2 | Server address, port, authentication value provided by the server, and any required TLS parameters. | Hysteria2 is based on QUIC and uses UDP. Enter SNI or obfuscation parameters exactly as provided. The server authentication value and obfuscation parameters belong in different fields. |
How to Check the Port and Transport
A port number tells you where a service accepts connections; it doesn't identify the protocol. For example, with the placeholder address example.com:443, the connection details might specify Trojan over TLS and Hysteria2. Even if both entries show the same address and port, check that Trojan uses TCP and Hysteria2 uses UDP. Changing one entry's Type to the other won't make the server accept a different handshake.
Bottom line: Distinguish Network Restrictions from Incorrect Fields
If the same Hysteria2 configuration works on cellular but repeatedly times out on Wi-Fi, leave the configuration unchanged and test again. Then ask your network administrator to check whether UDP traffic to that address and port is restricted. If you see a certificate error, check SNI, the system clock and the certificate first. Don't turn off certificate verification just to dismiss the error.
Global Routing: Separate Connection Issues from Routing Rules
Add Server determines how to connect to a server; Home → Global Routing determines how captured traffic is routed. Selecting a server doesn't mean every request goes through it. Under Config, traffic may match a proxy policy, DIRECT or REJECT. If no earlier rule matches, check which policy FINAL points to.
Config
RecommendedRoutes traffic according to the rules and policies in the current configuration. A destination may not use the entry currently selected on Home; it may follow a different policy specified by a rule.
Best for: Using your own routing rules day to day after confirming the server works
Proxy
Sends captured traffic through the proxy, bypassing the routing rules in Config. You can use this mode temporarily to test the same destination, then restore your previous setting.
Best for: Checking whether a problem is related to rules or policy selection in Config
Direct
Sends captured traffic directly, without using a proxy server. If a destination opens in this mode, that doesn't prove the proxy settings are correct.
Best for: Establishing a baseline without using a proxy
Importing, Saving and Troubleshooting Connection Problems
I only have a UUID. Should I choose VMess or VLESS?
A UUID alone isn't enough to tell. Check the original connection details for the protocol name. If you have a share link, the vmess:// and vless:// prefixes identify the type. A UUID by itself is missing other details, including the server address, port and transport. Ask the provider of the connection details rather than switching Types and guessing.
Do I need to enter each server again after importing a subscription?
No. A subscription URL retrieves and updates a group of entries; it isn't the address of a particular server. After importing a subscription, return to Home and check that the entries appear. If the parameters change, update the subscription first, then check the currently selected entry. Don't copy fields from an outdated entry into a new one.
Why does Add Server save successfully, but the connection still times out?
Saving only means the entry was stored; it doesn't confirm that the server is reachable. Compare the address and port with the original details, then check the Type and transport. For a WebSocket path, also check the leading slash and capitalization. Change one item at a time and record the result after each retry. If you get a clear authentication failure, check the credentials first rather than trying random ports.
Why does the same website open in Proxy but not in Config?
Keep the network and the server selected on Home the same, and test the same destination. If the difference is reproducible, return to Config and confirm which configuration is active. Check rules from top to bottom for an earlier match—for example, whether DOMAIN-SUFFIX sends the domain to a different policy. Check FINAL only if no earlier rule matches.