Submit tickets from the user panel for connection, route, subscription import, plan, or refund issues. The more complete your description, the easier it is to identify the relevant step during troubleshooting.
Tickets retain your issue description and follow-up replies, making them suitable for matters that require ongoing troubleshooting. Public email and Telegram contact details have not been published. Do not contact anyone using identity information provided outside this site.
Recommended
User Panel Tickets
Use this for connection failures, route changes, subscription imports, plan status, payment records, and refund questions. After submitting, check the status in the user panel and add screenshots or steps to the same ticket.
The site’s published facts do not include a public support email, so no unconfirmed address is shown. For account or subscription issues, use a ticket in the user panel.
The site’s published facts do not include public Telegram contact details. Use the entry points listed on this site and do not share order, subscription, or account information with unknown contacts.
Keep the information needed for troubleshooting in one ticket
For connection issues, include the platform you use, the target region, the selected route type, and whether the problem occurs before connecting, during connection, or after a successful connection. VPNBe supports Windows, macOS, iOS, Android, and Linux. Import screens and permission prompts vary by platform, so naming your platform helps reduce back-and-forth.
For subscription import issues, explain how far you got, what the page displayed, and whether the result changed after switching routes. A subscription URL is account information, so do not post it publicly. In a ticket, describe the symptoms first and provide the relevant details only when clearly needed for troubleshooting.
For plan and payment issues, specify the plan selected and payment method. The site supports Alipay, WeChat Pay, and USDT. For a refund, include the order details and reason for the request. The refund policy provides 60-day no-questions-asked refunds; follow-up status is recorded in the ticket.
How Issues Are Handled
Response flow by issue type
How are connection or route issues handled?
Support first checks the platform, route, and reported symptoms. When the information is complete, you will receive guidance on switching routes, importing again, or checking system settings. Issues that require reproduction will receive further follow-up after the relevant checks are completed.
What information is needed for plan, payment, or refund issues?
State the plan, payment method, and current order status in your ticket. Do not share complete subscription details or other sensitive account information publicly. Support will explain what additional information is needed based on the troubleshooting steps.
Why is there no instant result after submission?
Tickets are handled according to the details submitted. Reproducing a connection issue, verifying payment status, or checking routes may require the relevant troubleshooting steps before a conclusion can be provided, so no instant response is promised. Further updates remain in the same ticket.
Can I submit the same issue again?
For the same issue, continue adding information to the original ticket so the full context is preserved. If the symptoms have changed, describe the new result to avoid splitting information from different stages.