Start with how the pieces fit together: a subscription provides configuration, a node is a connection option, a protocol defines how the client communicates with the server, and routing determines which requests use the proxy. These are separate layers—a “connected” status alone doesn’t tell you whether everything is working.
Once you understand how these pieces relate, you can troubleshoot an import failure, a node timeout or an app that can’t connect layer by layer instead of endlessly changing settings. The protocols below are industry-wide concepts; they don’t mean VPNJiage supports every one. Check the dashboard and client documentation for current support.
Glossary: What Each Setting Does
| Term | What it means | Common point of confusion |
|---|---|---|
| Plan subscription | The billing and data allowance rules for using an account | Not the configuration URL you import into a client |
| Subscription link | A unique URL a client uses to fetch or update configuration | A successful import doesn’t mean a node is connected |
| Node | A connection profile in the client | The displayed region doesn’t reveal the full physical server route |
| Route | The network path and setup used by a connection | Not the same thing as a protocol name |
| Protocol | The rules for communication between a client and server | A newer protocol isn’t necessarily faster on your network |
| Routing rule | A condition that sends traffic direct, through a proxy or blocks it | A rule can only handle requests that reach the client |
In everyday conversation, “VPN” is often used as a catch-all for network acceleration tools. Strictly speaking, proxy protocols, system proxies and network-layer tunnels are different things. Some clients receive traffic through a local proxy port; others use a virtual network interface to handle it. An operating system’s VPN indicator doesn’t prove that a traditional VPN protocol is running underneath.
Subscriptions: Keep Billing Separate from Configuration Links
Your plan subscription sets the usage terms
A monthly subscription in the dashboard is a billing product. VPNJiage monthly plans are ¥9.9 / 60GB, ¥18 / 250GB and ¥28 / 500GB; data resets monthly on the activation date. Data packages are ¥158 / 300GB, ¥358 / 1000GB and ¥658 / 3000GB; they don’t expire and remain available until used. Check your dashboard for your balance, plan status and reset date.
So “update subscription” usually doesn’t mean renewing your plan or adding more data. The client is simply downloading the configuration again; account access is a separate check. See the Plans & Pricing page for current prices and terms.
The subscription link tells the client where to get configuration
A subscription link usually contains credentials unique to your account. When a client reads it, it gets a list of nodes or a complete configuration, which may also include policy groups, routing rules and DNS settings. Clients accept different formats, so a URL opening successfully doesn’t mean your client can parse its contents.
Keep your subscription link private: Don’t share it in public chats, screenshots or with unknown conversion sites. If you think it’s been exposed, reset the link as directed in the dashboard and import it again on each device. The old link may stop working after a reset; deleting the local configuration alone isn’t enough.
Subscription conversion changes one configuration format into another; it doesn’t fix account access or network routes. Conversion services may be able to access your full link, so use an export option explicitly supported by the dashboard whenever possible. Don’t treat an unfamiliar conversion site as a required step.
Nodes and Routes: Entry Points, Exit Points, and Network Paths
A node entry may include a server address, port, authentication details, protocol and transport settings. The region shown in a client usually indicates the intended exit location, not the full network topology. The entry point is where your device connects first; the exit is the network location seen by the destination website. Traffic may pass through other networks in between.
Direct connections, relays and IEPL links
- Direct: Your device connects to the destination proxy server without an extra relay entry point. Traffic still passes through your internet provider’s network, so there may be intermediate routes between your device and the server.
- Relay: Your device connects to a relay entry point first, which forwards traffic to another server. This may improve the route, but can also add overhead. Results depend on the entry point, inter-network paths and congestion.
- IEPL link: Generally refers to an international Ethernet private line—a type of underlying transport link. It isn’t a proxy protocol, and it doesn’t mean every segment from your device to the entry point or from the exit to a website uses a private line.
Distance alone doesn’t determine which route is best. Geography, provider peering, link load and the destination website’s network location all affect performance. Low latency doesn’t necessarily mean high download throughput. The latency shown by a client may only measure a response from a particular probe target, not the full time taken by real-world traffic.
When reviewing server and route details, check the actual node list in your dashboard to see what’s available. An exit in a given region doesn’t guarantee every website will recognise it as being there or allow access. Platform account region, licensing rules and fraud prevention checks can also affect access.
Protocols: How Data Travels, Not a Speed Ranking
A protocol defines how data is authenticated, encapsulated and transmitted. It’s separate from the route the connection takes: the same protocol can run over different routes, and a single route can carry different protocols. The client must support both the protocol and its specific parameter set.
- Shadowsocks: An encrypted proxy protocol. Its encryption method and other parameters must match what the server supports. It isn’t a full network-layer VPN.
- VMess: A proxy protocol with authentication and encryption. Common implementations require accurate system time; a significant clock mismatch can prevent a connection.
- Trojan: Usually runs over TLS. The server name, certificate verification and server configuration need to match; copying the password alone isn’t enough.
- VLESS: A lightweight proxy protocol that doesn’t provide the same built-in encryption as VMess. Deployments commonly pair it with a security layer such as TLS or REALITY; the name alone doesn’t guarantee encryption.
- Hysteria2 and TUIC: QUIC-based proxy protocols that depend on UDP network conditions. If UDP is restricted on your current network, they may not connect even when your account is working normally.
Transport is a separate setting—for example, TCP, WebSocket or gRPC. Which combinations are available depends on the implementation. The same protocol doesn’t guarantee that every client can import a configuration: client core versions, extra parameters and configuration syntax may differ.
Don’t disable certificate verification casually: If you see a certificate or TLS error, first check your device’s clock, server name and configuration source. Skipping verification weakens identity checks and isn’t a general-purpose connection fix.
Routing, Global Mode, and TUN: What Each One Handles
Rules determine where traffic goes; capture methods determine what gets covered
Rule mode uses domains, destination addresses or other supported conditions to send requests direct, to a proxy policy group or to a block. Many clients check rules in order, so an earlier rule can take precedence over a later one. When troubleshooting, check which rule actually matched—not just whether the target domain appears in the list.
Global mode usually sends requests that enter the client’s proxy flow through the selected proxy policy. It doesn’t automatically capture every app. If an app ignores the system proxy, switching to global mode may not change its route. Some clients also handle exceptions in their own way, so check the software documentation.
A system proxy tells compatible apps to use a specified proxy. TUN mode uses a virtual network interface and routing to capture traffic, usually covering more apps, but it depends on system permissions, routes and DNS settings. TUN isn’t simply an “advanced global mode”; it can be used alongside rule mode.
Why DNS can affect what you can access
DNS translates domain names into network addresses. Sending a request through a proxy doesn’t necessarily send its DNS lookup through the same route. A DNS leak can occur if a lookup intended to use a specified resolution path is unexpectedly sent to the local resolver instead. First establish the expected path before deciding whether a leak occurred; seeing a local internet provider in a result isn’t enough to draw a conclusion without checking the configuration.
A browser’s secure DNS, the system resolver and the client’s DNS settings may all take part in lookups. Check client logs and the active rules to see where queries go. Encrypted DNS protects the lookup in transit, but doesn’t guarantee it uses the proxy exit or hide every aspect of your browsing activity.
Troubleshoot in this order: First check whether app traffic reaches the client, then see which rule matched, and finally check the selected node and DNS route. Global mode, rule mode, system proxy and TUN aren’t interchangeable switches.
Client Setup: Check Platform and Format
Platform differences mainly come down to installation sources, permission models and how traffic is captured. App availability in the iOS store can depend on your account region. On Android, traffic capture may conflict with other apps that use the system VPN interface. For Windows, macOS and Linux, check system proxy settings, virtual interfaces and required permissions separately; button locations don’t necessarily match across platforms.
Check compatibility details at the client download page, then follow the quick start guide. Similar names don’t mean clients on different platforms use the same core or support every protocol.
- Check your account status: Confirm your plan status and available data to rule out an access issue before troubleshooting configuration.
- Choose the right format: Select the subscription option in the dashboard that matches your client. Check whether you need to import nodes or a complete configuration.
- Import and check the result: Make sure the node list appears without parsing errors. Grant any required network permissions as prompted by your system and described in the official documentation.
- Choose a node and mode: Start with the default recommended configuration to establish a connection. Avoid changing the protocol, DNS and routing all at once, which makes problems harder to isolate.
- Test with the app you actually use: Open the target website and check the client’s connection logs and matched rules instead of relying only on a test button.
There’s no need to set an arbitrary fixed schedule for updating a subscription. Refresh it when the server changes nodes, your list looks clearly outdated or an official notice asks you to. A successful update only confirms that the configuration was retrieved; it doesn’t verify that the service works with your apps.
Troubleshooting Quick Reference: Match Each Error to the Right Layer
- ✅ Import failed: Check that the link is complete and the format is compatible. Look for authentication or parsing errors; don’t assume the route is slow.
- ✅ All nodes timed out: First confirm that your local network is online, then check your account status, device clock and client compatibility. If needed, switch routes as directed by the service documentation.
- ✅ Connected, but an app can’t connect: Check whether the app’s traffic enters the proxy flow, which rule matched and how DNS is routed. Also check separately for sign-in verification, regional restrictions and website outages.
- ✅ Only one node is having issues: Under the same app and network conditions, try another node from the dashboard and keep a record of the error. Don’t judge the entire service based on a single result.
- ❌ Don’t share full logs publicly: Before reporting an issue, redact your subscription link, authentication details and account information. Tell support your platform, client version, what happened and what you’ve already tried.
A no-logs policy describes a service’s approach to privacy; it doesn’t mean your device has no local diagnostic logs or prevent your browser’s sign-in state and websites from collecting data. Use local diagnostic information when needed for troubleshooting, but limit what you share. If you can’t identify a configuration error, contact support via the Support page.
Keep the key steps in mind: Your plan provides access, the subscription provides configuration, and the node and protocol establish a connection. Traffic capture and routing rules determine where requests go. Checking each step in order is more effective than switching every setting back and forth.