Connection help
How to Write a VPN Support Report Without Sharing Secrets
Give VPN support the version, symptom and reproduction steps they need while keeping supercodes, private configuration and unrelated personal data out of your report.
Start with the symptom you can describe
A useful VPN support report starts with what happened, what you expected and the point where the two differed. “It does not work” leaves too many possibilities open. “The location list did not appear after opening the app” identifies a different problem from “the app showed a connection, but one website would not load.” Keep that distinction visible so that support can ask a focused next question.
Write two or three sentences before attaching anything. Name the action, the visible result and whether the problem repeats. The JungleVPN connection help centre separates installation, supercode and connection questions. Start with the route that matches your symptom. You do not need to diagnose the underlying cause yourself, and a useful first report does not need a complete device archive.
Include the release, device and time
Record your operating-system version, device type and the app version actually installed. Use the version shown by your own build rather than copying a number from a website screenshot. Include the time of the problem and its time zone. A short note such as “around 09:20 Bangkok time” is more useful than “this morning” when the person investigating works somewhere else.
Check the Android release and setup information or the Windows release and setup information when describing how you obtained the package. These pages currently direct release enquiries to the team. Do not assume that a recorded app image identifies an approved installer for your device. If the package or signing information is unclear, describe that uncertainty instead of inventing a version.
Keep reproduction steps short and proportionate
List the smallest sequence that leads to the symptom. For example, opening the app, selecting an available location and seeing a particular non-sensitive message is a clearer account than a long story about every setting you have tried. Record whether the device was using Wi-Fi or mobile data and whether the underlying internet connection was usable. A network name, home address or browsing history is usually unnecessary in an initial public report.
Change one relevant thing at a time if you make a comparison, and note the result. Do not repeatedly clear data, remove access or reinstall software just to produce a longer list of attempts. Preserve the original observation. If the symptom occurs only on one network, say so without claiming that you have proved its cause. Ask support before taking a step that could discard useful state or affect an entitlement.
Ask which diagnostic information is needed
Diagnostic files can cover more than the visible error. The Android Open Source Project’s guide to reading Android bug reports describes system-service output and several kinds of logs. A whole-device report is therefore a different attachment from a cropped image of one app message. Ask whether a short excerpt, a timestamp or a particular file is needed before collecting a broad archive.
Use the JungleVPN privacy and diagnostics disclosures to understand the current distinction between app diagnostics, activation records and other operational information. This article does not assume that every release has the same export control or that every log is automatically redacted. If support requests a file, confirm the intended channel, what it contains and how to remove unrelated personal information before sending it.
Keep credentials and activation information out of the report
Do not include passwords, supercodes, bearer tokens, private keys, recovery information or complete VPN profiles in a public post. The WireGuard project’s key-generation and configuration documentation distinguishes public and private keys and shows that configuration can reference a private key. Treat a configuration attachment as something to inspect carefully, rather than assuming it is harmless because it looks like plain text.
The JungleVPN supercode activation steps explain the one-use code and its five-minute entry window. Support can ask about the time of an activation attempt without you posting the code itself. If a message includes both an error and a credential, preserve the error wording while removing the credential. Do not attach the original unredacted file beside the cleaned copy.
Make screenshots readable and limited to the issue
Capture only the area needed to show the symptom. Inspect the image for account names, notifications, browser tabs, email addresses, local file paths and anything else unrelated to the question. A useful crop can show the message and enough surrounding interface to explain where it appeared. Review the saved image before attaching it; do not assume an editing overlay has removed the underlying information from every copy.
The real JungleVPN app screenshots show dated interface captures, which can help identify which screen you mean. Your report should still describe your own version and current observation. Avoid adding labels that make a hypothetical example look like a genuine app error. If you cannot safely share a screenshot, a short transcription of the non-sensitive wording may be enough for the first reply.
Send a compact report and keep follow-up changes visible
A practical first message can include: the device and app version; the approximate time and time zone; the action; the expected result; the observed result; whether it repeats; and one relevant comparison. Keep this in a single readable account. Label any example clearly, and distinguish what you observed from what you suspect. That helps support avoid treating an assumption as a confirmed connection failure.
Use the team contact linked from JungleVPN’s help pages for an access or release enquiry. If you later update the app or change networks, add a dated follow-up rather than replacing the original facts without explanation. A focused report can become more detailed as the investigation needs it. The aim is enough evidence to answer the next question, with private information kept out of the conversation unless a specific, appropriate handling route has been agreed.