VPN Beginner FAQs: 10 Common Questions Answered

Question 1: How do a VPN, a client app, and a subscription work together?

In everyday use, “VPN” sometimes refers broadly to subscription services for routing internet traffic, but the underlying technology varies. A system VPN typically routes traffic through a virtual network interface. A proxy client may set a system proxy or route network traffic through TUN mode. Seeing a VPN icon in the status bar doesn’t mean every app is using the same route.

Think of the service as providing routes and account access, the client as the software that connects to them, and the subscription as the configuration source the client reads. Installing a client doesn’t give you access to routes, and having a subscription doesn’t mean your device is connected. To get started, prepare your account, install a client, import the configuration, and verify your exit route.

VPNEG requires no email address; you can create an account with a username and password. Your account password is for signing in to the dashboard, while your subscription link is for importing a configuration. Keep them separate and use a unique password that you don’t reuse on other sites.

Question 2: Can you use multiple devices at the same time?

VPNEG has no limit on the number of devices online at once. You can install a compatible client, import the configuration, and connect on each device, such as a computer or tablet, without signing out because another device is in use. This unlimited-device policy doesn’t mean unlimited data, or guarantee the same performance across different networks.

Devices on the same account share the plan’s data allowance. Background file syncing on a computer or video streaming on a tablet can both affect your remaining data. If usage seems higher than expected, check background activity and routing settings on all your devices—not just the one you’re currently using.

Don’t post your subscription publicly in group chats or on forums for convenience. It contains connection credentials, and if they’re exposed, someone else could use your data. For router-wide access, also check the router’s performance, client compatibility, and local network routing settings.

Question 3: How is data usage counted, and which plan should you choose?

Data sent through the service counts toward your allowance. Factor in video, downloads, cloud syncing, and uploads when estimating your usage. The size of a downloaded file won’t always match the amount billed: protocol overhead, retransmissions, and differences in how usage is measured can make your device’s figures differ from the dashboard. The user dashboard shows your remaining data.

VPNEG monthly subscriptions reset each month on the date you subscribed, not at the start of the calendar month. Data packages remain available until used and never expire. A monthly subscription may suit regular users, while a data package may work better if your usage is occasional. Don’t compare data allowances alone—consider whether you’ll use the data before the reset.

Before choosing a plan, check recent data usage on the devices you use most and work out which traffic actually goes through the proxy. Your device’s total usage includes direct connections, so it won’t match your subscription usage exactly. See the plans page for all available options.

Question 4: Does a slow connection mean your speed is being limited?

One video buffering event isn’t enough to conclude that the service is limiting your speed. Wi-Fi interference, your ISP’s routing, congestion on an exit route, the destination site’s load, and device performance can all be bottlenecks. Low latency means a short round-trip wait, not necessarily fast sustained downloads. Speed test results also don’t replace real-world app performance.

Start by checking whether your local connection works normally with the proxy disconnected. Then keep the device and destination site the same, switch routes, and compare the results. Next, test other destination sites. This helps pinpoint whether the issue is local, route-specific, or limited to a particular site. Don’t change the protocol, DNS, and routing mode all at once, or it’ll be hard to identify the cause.

“Direct,” “relay,” and “IEPL dedicated line” describe how routes are set up, not speed tiers. A direct route typically skips a relay entry point run by the service provider; a relay adds an extra forwarding hop; IEPL refers to a dedicated Ethernet line. Even on a dedicated line, the entry point, exit point, and destination site can affect performance. A route label isn’t a performance guarantee. See the routes and protocols guide for more background.

Question 5: Should it stay on all the time, and how do you choose split tunneling?

Whether to leave it on depends on how you use it. Connecting only when you need a particular service is easier to manage. If you often switch between sites, you can leave the client running and use rule-based routing. The client running, the proxy connected, and all traffic going through the proxy are three different states.

Rule-based mode uses domains, addresses, or other criteria to decide whether traffic connects directly or through the proxy. Global proxy mode generally sends traffic the client can intercept through the selected exit, but it doesn’t necessarily capture every app on the device. Some apps don’t follow the system proxy and may need a compatible TUN mode or system-level routing.

For your first setup, use rules provided by the service that match your client. Avoid stacking rules from unknown sources. If sites in mainland China take an unexpected route, local network devices become inaccessible, or an app can’t connect, check which rule matched. What happens after disconnecting varies by client. If you need ongoing protection, check whether the client has a kill switch and how it behaves.

Question 6: What is a subscription link, and how do you import it?

A subscription link is an address that lets a client retrieve nodes, connection parameters, and related configuration. It isn’t a regular webpage URL. Clients may support different subscription formats, so a link won’t necessarily work in every app. Before importing, check the client name, supported formats, and required protocols.

1. In your VPNEG dashboard, find the subscription link for your client and copy the full URL.
2. In the client, open the relevant option, such as “Subscription,” “Configuration,” or “Import from URL,” then paste the link and save it.
3. Update the configuration and confirm that selectable nodes appear; a saved entry with no nodes isn’t enough.
4. Enable the configuration, select a node, then turn on the system proxy or follow the guide to enable network routing.
5. Visit a service you want to use and check your exit information to verify the traffic route.

Treat your subscription link like a connection credential. Before sharing an error screenshot, hide the full URL, token, and QR code. If you suspect the link has been exposed, check whether the dashboard lets you reset it. If you’re unsure, contact support through a ticket. Don’t post the original link in public discussions.

If an update fails, first check that the link hasn’t been cut off, your account is active, and the client can reach the subscription address. Don’t “fix” an import problem by disabling certificate verification. For certificate errors, check your device’s date and time, where the address came from, and your client version.

Question 7: Are newer protocols always better, and what should you use on each platform?

Choose a protocol based on what the server offers and the client supports, then consider whether it suits your current network. Trojan typically uses TLS for transport. VLESS doesn’t provide encryption on its own; security depends on the configured transport and security layers. Hysteria2 and TUIC use QUIC and depend on UDP network conditions. A protocol name alone doesn’t prove that a connection will be faster or more stable.

Shadowsocks and VMess are also common in proxy client ecosystems. But seeing them in an app’s support list doesn’t mean they’re available in your current subscription. VPNEG supports Trojan, VLESS, Hysteria2, and TUIC. Use the configuration actually provided—don’t just change a protocol name or guess the parameters.

Windows, macOS, Android, and iOS clients differ in how they’re installed, the permissions they request, how they run in the background, and how they route network traffic. Features with the same name can also work differently. Check the platform details in the quick start guide first, then get the app from a trusted source. Adjust advanced settings only after the import succeeds.

Question 8: Why can’t I access anything when the client says it’s connected?

“Connected” usually means the client has enabled a feature; it doesn’t prove that the target app is routing traffic correctly. Common causes include the wrong configuration, the system proxy being off, a rule sending the destination through a direct connection, DNS resolution failure, or an issue with the site itself.

• ✅ Make sure the configuration you just imported is enabled and that you’ve selected a working node.
• ✅ Check that the system proxy or TUN mode is actually on, and grant the permissions required by your platform.
• ✅ Try the destination in a browser and in the original app to see whether the problem is limited to one app.
• ✅ Check the client logs for DNS, handshake, or timeout messages. Note the exact error before changing settings.
• ✅ Try another route for comparison, and check whether another proxy app or network extension is also routing traffic.
• ❌ Don’t assume every error is caused by a node, and don’t change every advanced setting at once while troubleshooting.

When contacting support, include your device’s operating system, client name, exact error message, and what you were doing. That’s more useful than simply saying “it doesn’t work.” Before submitting logs, check them for subscription credentials or private browsing activity.

Question 9: How do you verify your exit route, and what is a DNS leak?

Before and after connecting, use network diagnostics to check whether your browser’s exit IP address and region changed as expected. This result only reflects that specific test request; it can’t confirm that other apps, protocols, or background connections use the same route. With rule-based routing, different sites using different routes may be normal.

DNS translates domain names into addresses. A DNS leak generally means a lookup that was expected to be protected or routed as configured instead went through an unexpected local or ISP path. Seeing resolvers in different regions in a test doesn’t prove there’s a leak on its own. Check the client’s DNS settings, routing rules, and your browser’s encrypted DNS settings too.

When troubleshooting, don’t just switch DNS to a public address. First check whether the client handles DNS, how domain rules are matched, and whether your browser uses its own DNS settings. Check IPv6 too, in case the proxy only routes some connections. If you don’t have a specific need, stick with the recommended setup and change one setting at a time to address a reproducible issue.

Question 10: Does connecting make you completely anonymous?

No. A proxy or VPN can change the route for some traffic and protect data on applicable connection segments, but it doesn’t erase website accounts, cookies, device fingerprints, or information you submit. If you sign in to an existing account, the platform can still identify it. Changing your browser’s exit route doesn’t remove app permissions or erase your history.

On public networks, check that sites use HTTPS, take certificate warnings seriously, and keep your operating system and client up to date. A service’s no-logs policy is a statement about its privacy practices; it doesn’t replace device security or mean that websites and your device keep no records.

When choosing a service, look beyond connection quality: check whether its policies are clear, whether support is available, and what its refund terms are. VPNEG offers a 14-day, no-questions-asked refund. For specific questions, start with the FAQ, then contact support through a ticket in your user dashboard.