Troubleshoot connection failures, slow speeds, disconnects, and verification codes

Troubleshooting should locate the layer where a failure begins. Change one condition at a time. Reinstalling the client, changing several rules, or resetting the subscription first can erase useful evidence.

Check in this order: account → subscription → client → node → current network → destination website.

Define the scope first

1. Open the Dashboard, confirm that the plan is active and traffic remains, and note the next traffic reset time.
2. Update the current remote subscription once and record whether it succeeds or shows a specific error.
3. Determine whether one node, a few nodes, or every node fails.
4. Determine whether one website fails or ordinary HTTPS websites also fail.
5. Keep the client configuration unchanged and compare Wi-Fi with mobile data.
6. If another configured device is available, check whether the problem affects one device or several.

For plan, order, or traffic status, see Choose, purchase, and activate a subscription. For import or update failures, see Import your subscription into a client.

Five-minute recovery sequence

1. Record the exact time, time zone, network type, and complete visible error before changing anything.
2. Confirm that only one network client is running; exit other proxy or VPN tools.
3. Set the device date, time, and time zone to automatic and confirm that they are correct.
4. Update the existing subscription once. If the client reports 429 or too many requests, stop and wait a few minutes before one retry.
5. Select another node shown as online and test an ordinary HTTPS website.
6. Fully exit and reopen the client, then compare Wi-Fi with mobile data without changing other settings.

Test after every step. Do not change the client, node, rules, and DNS together, and never disable certificate verification to bypass a TLS warning.

Continue by symptom

Every node fails

Check the plan, remaining traffic, last subscription update, device clock, and client conflicts. If the same configuration fails across multiple devices and both Wi-Fi and mobile data, record the shared error and open a ticket. Repeated subscription resets are not a diagnostic method.

Only one or a few nodes fail

Try other nodes shown as online and record the failed node's complete displayed name, the time, and network type. If other nodes work, the account and subscription are probably still usable; one failed node does not mean the entire plan has failed.

The client says connected, but pages do not open

Confirm that the client's connection, system proxy, or VPN mode is actually enabled and that another client has not taken control. Test an ordinary HTTPS website before deciding that every destination is affected. Do not rebuild the whole configuration because one website fails.

Speed is slow, latency is high, or video stalls

Pause system updates, cloud synchronization, background downloads, and heavy activity from other devices. Compare a small number of online nodes on the same device, network, and approximate time. A node multiplier affects traffic deduction, not a proportional speed increase. The destination, Wi-Fi signal, and device performance also matter.

The connection repeatedly drops and reconnects

Check weak Wi-Fi, switching between cellular networks, battery-saving restrictions, permission to run in the background, and conflicts with another VPN or network tool. Change one item and observe before trying another; do not repeatedly re-import the subscription.

Wi-Fi works but mobile data fails, or the reverse

This first points to a difference in the current access network or route, not necessarily the account. Keep the node and client settings unchanged while comparing networks. Do not install unknown profiles, choose random DNS settings, or weaken security controls.

Verification email does not arrive or sign-in fails

1. Check the email spelling before sending. Registration, code delivery, and code submission must use the same address.
2. If the page shows a security check, complete it before selecting Send. If the widget does not load, disable content blocking, change networks, or refresh the page.
3. After a successful send, wait at least one minute, check Spam and Promotions, and search for SNSCDN. Mark a found message as not spam.
4. A verification code currently remains valid for about five minutes. A successful resend replaces the previous code, so use the six digits in the newest message rather than mixing several emails.
5. Repeated Send, Register, Sign in, or password-reset requests can trigger a cooldown or 429. Stop repeating the action and wait for the page timer or try later.
6. If email succeeds but registration reports 503, maintenance or read-only mode may permit page reads and email while temporarily blocking registration writes. Stop submitting, then request a new code and register after service recovers. If the verification or email step itself is unavailable, keep the time and exact error and retry later.
7. If the address already exists, use Sign in or Forgot password instead of registering it again.

If email still does not arrive and you cannot sign in, use the public support page or email support@snscdn.com. Include the recipient domain, send time and time zone, network type, and visible error—never the mailbox password or a verification code.

Subscription update fails, nodes are empty, or 401/403/429 appears

1. If a subscription update reports 401, 403, or a download error, first confirm that the plan is active and traffic remains, then sign in to the Dashboard again and copy the current URL. Do not edit the URL; replace the old remote profile only if the complete Dashboard URL has changed.
2. A 429 response means too many requests in a short period. Stop refreshing, wait a few minutes, and update once; do not make several devices refresh at high frequency.
3. If an update succeeds but the node list is empty, confirm that the order is complete, the plan is active, and traffic remains before importing the current URL again.
4. If one-click import opens the wrong client, cancel it and use Import from URL inside the intended client.

See Import your subscription into a client for complete one-click and manual steps. Interpret an error in context: a 401 on the sign-in page is not necessarily the same problem as a 401 during subscription refresh.

Distinguish DNS, TCP, TLS, and HTTP failures

1. DNS failure: the device did not resolve a public hostname. Check the spelling and compare two networks; one failure does not prove that a server is offline.
2. TCP timeout or unreachable port: the name may have resolved, but the connection to the destination port did not finish. The cause may be the device, access network, route, or remote service.
3. TLS or certificate error: check the device clock and hostname. Do not ignore the warning or disable verification. An intermediary on the network can also affect the handshake.
4. HTTP 4xx: the request reached the application layer but may have been rejected because of the session, permission, credential, or request format. This does not mean the network is completely unreachable.
5. HTTP 5xx or 503: the service could not process the request normally. During maintenance or read-only mode, pages and verification email may work while registration, purchase, or ticket writes remain blocked. Wait for recovery instead of repeating payment, order, registration, or refresh actions.
6. Every check passes but the application still fails: this shows only that the basic test passed at that moment. It does not validate the client configuration, bandwidth, or long-term availability from every region.

Use only a public hostname for a network check. Never test a complete subscription URL, token-bearing URL, administration address, or private IP, and do not post a complete diagnostic log in a public group or issue.

Speed, latency, packet loss, and traffic are different

1. Latency is response time; one result does not describe all-day quality.
2. Packet loss and jitter are more likely to cause stalls, interrupted streams, and reconnects even when peak throughput looks high.
3. Throughput also depends on the destination, device performance, Wi-Fi signal, and background traffic. Compare only a few tests under the same conditions.
4. SNSCDN counts both upload and download and applies the node multiplier. Faster traffic deduction does not prove a faster route. See the purchase guide for details.

When to reset subscription information

1. Reset it immediately if the complete subscription URL or QR code was public, appeared in an unredacted screenshot, or may have been used by someone else.
2. If the complete Dashboard URL has changed or the platform announces a security or operational credential rotation, use the current Dashboard entry and re-import it on every device.
3. Do not reset first for one failed node, ordinary slow speed, a temporary 429, or one unavailable website. A reset invalidates the old credentials saved by every device.

After a reset, follow the client import guide on every device. Renaming a profile does not revoke an exposed credential.

Submit a ticket that can be diagnosed

The panel allows only one unresolved ticket at a time. If one is pending, review it and wait; continue there after support replies instead of opening a duplicate. A new ticket requires a subject, priority, and problem description.

1. Include the date, exact time, and time zone.
2. Include the device model, operating system and version, and client name and version.
3. State whether you used Wi-Fi or mobile data and what happened after switching networks.
4. State whether one or every node, website, and device is affected.
5. Copy the complete error text into the description. The ticket form has no separate attachment field; if a screenshot is necessary, email a redacted attachment to support@snscdn.com and name the existing ticket number or subject.
6. List the steps already taken and the result after each one.
7. Include an order number only for order or payment issues, and never attach complete payment credentials.

Time and time zone: ; device and OS: ; client version: ; network: ; scope: ; exact error: ; steps tried:

Send this through My Tickets and select the create action; in some current translations that button may repeat the page title. Never include a password, email verification code, complete subscription URL, QR code, access token, card data, or unredacted account information. If you cannot sign in, use the public support page or support@snscdn.com with the same redaction rules.

Use SNSCDN only in compliance with laws that apply where you are located and where the service is used.