Plain VPN

What Information to Prepare Before Contacting VPN Support

Clear, reproducible information helps support distinguish account, payment, client, and network problems. A report that only says “it does not work” or “payment is missing” usually requires several follow-up questions. Prepare the relevant details below while protecting sensitive information.

1. Information useful for every issue

  • approximate time of the problem;
  • whether the Chinese or English page was used;
  • device type and operating-system version;
  • browser or client used;
  • complete visible error message;
  • whether the issue can be repeated;
  • troubleshooting steps already tried.

Before sending a screenshot, hide passwords, verification codes, payment secrets, private email content, and unrelated personal information.

2. Order problems

Prepare:

  • order number;
  • plan name;
  • current order status;
  • order creation time;
  • whether several similar orders were created;
  • related information shown in the account center.

Do not create or pay for another order just to test the status.

3. USDT payment problems

Without exposing wallet secrets, provide:

  • order number;
  • transaction hash;
  • network used;
  • amount sent;
  • transfer time;
  • on-chain confirmation state.

Never send a seed phrase, private key, wallet password, or exchange login code.

4. Website sign-in or registration problems

Provide:

  • a partially masked registration email;
  • approximate time of the code request or registration submission;
  • page message;
  • browser and device;
  • whether a private window was used;
  • whether spam folders were checked.

Support does not need the website password or verification code.

5. VPN client sign-in problems

Provide a partially masked VPN username, whether the service has expired, the exact error, and whether the VPN password was recently changed. Do not provide the current password.

Confirm first that a website password was not mistakenly used as the VPN password.

6. Connection or performance problems

Include:

  • Wi-Fi, mobile data, or wired connection;
  • whether every site or one site is affected;
  • device and system version;
  • client connection state;
  • selected server;
  • a repeatable comparison before and after connecting;
  • whether another VPN, proxy, or network filter is running.

Avoid sending one speed number without the test conditions.

7. Expiry or renewal problems

Prepare the recent order number, expiry date shown in the account center, date in the official notification, and client message. Do not change local records or purchase repeatedly to alter the date.

8. Information never to send

  • website or VPN passwords;
  • email verification codes or password-reset links;
  • API keys, payment secrets, or administrator credentials;
  • wallet private keys, seed phrases, or wallet passwords;
  • full payment-card information;
  • information belonging to another customer.

Frequently asked questions

Can I send a screenshot?

Yes, after cropping or hiding passwords, codes, full email addresses, wallet secrets, and unrelated notifications.

Why does support need an approximate time?

It can help correlate an order, email, and service record without requiring a complete sensitive log.

Why is “cannot connect” not enough?

Sign-in failure, base network failure, server conditions, and a single-site problem require different checks. The exact error and device details reduce unnecessary steps.

---

发布前统一检查清单

  • 中英文各自使用自然表达,不做逐字机械翻译;
  • 每篇只设一个 H1,正文使用清晰 H2/H3;
  • 标题、Meta 描述、摘要和浏览器标签均按语言显示;
  • 内链只指向实际存在的官网页面;
  • 不写死价格、USDT 地址、节点、协议或到期规则;
  • 不承诺固定速度、固定到账时间、绝对安全或必然解锁;
  • 文章链接文字用可识别的品牌蓝色并保持键盘可访问;
  • 发布后逐页检查中文、英文、手机和电脑页面;
  • 提交站点地图后,明确区分“已提交”和“已收录”。