Submit tickets from the user panel for account access, subscriptions, payment results, refunds or international route issues. Include your platform, route name and the symptoms you encountered for more direct troubleshooting.
User-panel tickets are currently available for direct support. Email and Telegram will only be used as contact methods once officially published on this site. Account and subscription issues are not handled through undisclosed accounts.
Use tickets for account access, subscription status, payment results, refund requests, client imports and international route troubleshooting. Include your platform, selected region, symptoms and steps already tried.
Submit a ticket →VPNYH has not currently published a support email on this site. For account, subscription, payment or refund issues, use a user-panel ticket and follow the official contact option shown there.
VPNYH has not currently published a Telegram support account on this site. Submit route and subscription issues through the user panel, and do not share account details with accounts not shown on this site.
Response times depend on the ticket queue, issue type and completeness of the diagnostic information; no fixed response time is promised. The more specific your description, the sooner it can move into review.
Provide your username, current subscription status and the items that need checking. Sign-up uses a username and password, with no email address required. Do not paste your full password or payment credentials into a ticket.
Specify whether you are using Windows, macOS, iOS, Android or Linux, and include the route region, client message and circumstances in which the issue occurs. If the symptoms change after switching routes, mention that as well.
Payment results for Alipay, WeChat Pay and USDT can be checked through a ticket. Refund requests are handled under the 30-day refund policy; select the relevant issue type and describe the order details.
Cross-platform differences, access to specific international websites or persistent connection issues usually require a step-by-step review of route and client information. Add context to the original ticket so the same issue can continue to be handled there.
A ticket does not need to be a long report. Keeping the key context together is more helpful than writing only “it does not work.”