By LitronSSHPublished 17 November 2026How we write and check our guides
When something on our servers stops working, the report form is how you tell our team about it. A useful report names the exact server, says what you saw and when, and leaves your secrets out. That saves a round of questions before anyone can act.
This guide goes through the form field by field, with a template and a made-up example. Then it explains what happens after you send it: the reference, the tracker, email replies, and following a report from another phone or browser.
Three checks before you write
The report page lists these quick checks next to the form. Each one can save you a wait:
- Is the server Offline or in Maintenance? Look it up on server status. If it is, our team already knows; use another server until it is back. How to read the server status page explains every state.
- Has the account expired? My accounts shows the time left for each account created in that browser, and whether the server removed one early.
- Does another listed port work? Account details often list more than one port. If you already have an account on another server, try that one too. Whatever works, say so in your report: it narrows the cause down.
If none of these explains it, Fix connection problems covers the usual setup mistakes. Then write the report.
Open the form from the right place
These links lead to the form. The first one fills part of it in for you:
- A server page: the server's details card ends with Report a problem with this server. The form then opens with that server and its service already chosen, and the page header names them.
- My accounts: the Account not working? Report a problem link at the bottom of the page.
- Any page: Report a problem in the site footer opens the report page with nothing chosen.
Which server? is optional. The list groups every listed server under its service, with a choice such as Any SSH server for each service and Not sure / general problem at the top. Pick the exact server when you know it; as the form says, it helps us find the problem faster.
Choose the category that fits
What's wrong? is required. Each option carries a short hint, and the last column below is what to mention for it.
| Category | The form's hint | Worth mentioning |
|---|---|---|
| Can't connect | The app won't connect or drops right away. | The app, the mode and port, and the last lines of its log. |
| Slow or unstable | Connected, but slow or unstable. | When it happens, Wi-Fi or mobile data, and whether another server feels the same. |
| Account not working | Login rejected or the details don't work. | The username, and the status the account shows on My accounts. |
| Something else | Anything else we should know. | What you saw and where, for example a page of this site that shows an error. |
Describe the problem: a template
Describe the problem needs at least 10 and at most 2,000 characters, and a counter beside the label shows how many you have used. Its placeholder sums up the essentials: what happened, which app and port you used, and since when. A useful description covers these points, in any order:
- When: when it started and when you last tried, with your time zone, such as 21:40 UTC+7.
- The app: its name, and its version if you can find it.
- How you connect: the mode, such as SSH with SSL/TLS on or an imported V2Ray link, and the port.
- What you see: the exact error message, or the last lines of the app's log, copied as text.
- Where: Wi-Fi or mobile data, and whether it behaves the same on another network you are allowed to use.
- What you tried: another listed port, copying the details again, an account you already have on another server.
- Which account: the username as your details or My accounts show it, never the password. Our team can look an account up by its username.
Screenshots, logs and other files
Attachments are optional, but the form says a screenshot of the error helps us most. What it accepts:
- Up to four files: screenshots or photos, PDFs and plain-text logs (.txt or .log).
- Up to 10 MB a file and 25 MB together. A text log can be up to 1 MB.
- Files dragged onto the box, picked with browse, or added by tapping the box on a phone. On a computer, Ctrl+V (⌘V on a Mac) pastes a screenshot straight into the form.
Large pictures are made smaller in your browser, to at most 2,000 pixels on the longest side, and our server saves every picture again without its hidden details, such as the camera model or where a photo was taken. PDFs and logs are kept as you sent them. Only our team can open the files; when you track the report, you see their names and sizes, not the files.
Your email, and what happens when you send
Your email is required. It is used to answer this report and to let you follow it from another device, and for nothing else. When this site emails its replies, the note under the field says so.
Complete the security check if one appears, then press Send report; with files attached, the button shows the upload's progress. A thank-you card then shows:
- A reference such as #1A2B3C4D: eight characters, made of digits and the letters A to F. Note it down and keep it private, because together with your email it opens the report and our replies on any device.
- Your address, when email replies are on, with a reminder to look in your spam folder if nothing arrives.
- Track this report, which opens the tracker with the new report at the top.
This browser now follows the report by itself, with no sign-up. It keeps a private tracking code, the reference, when you sent it and when you last viewed its progress, but not your message or your email.
Following your report
The Track your reports tab on the report page lists every report this browser follows. Each card has a progress line with three steps:
| Step | The card says | What it means |
|---|---|---|
| Sent | In the queue · Waiting for our team | The report has arrived and is waiting to be opened. |
| In review | In review · Our team is on it | Our team has opened the report and is looking into it. |
| Resolved | Resolved · Fixed and resolved | Our team has marked the problem resolved. |
- Status history lists each step with its date and time. A reply from our team appears there as a message signed with this site's name and the word Support, with a blue verified badge.
- Your message opens what you sent, with the names of any files.
- New updates are easy to spot. The tracker refreshes every minute while it is open, a card with news says Updated since your last visit, and the tab shows a dot while there is something you haven't seen.
- Stop following takes a report off this browser's list, with an Undo. The report itself stays with our team.
A report can't be edited once it is sent. If something important changes, or a resolved problem comes back, send a new report and mention the old reference; a resolved report's history suggests the same. If our team needs more details, they email you.
Email replies, and other phones or browsers
When this site has email replies switched on, our team can email you when it replies to your report and when it resolves it. The subject names the reference, as in We've replied to your report #1A2B3C4D. The email carries the reply, your message, the reference and a View your report button, never a password or key. The tracker shows the reply either way.
View your report opens the report in whichever browser you tap it in, and that browser follows it from then on. Answer by email only when the email invites you to; otherwise send a new report.
Without the email at hand, open Track your reports and use Track a report from another device: enter the reference and the email address you sent the report with, and the report joins that browser's list.
- Each browser gets its own tracking code. The browser you sent the report from always keeps its place. Other browsers share a few more places, and the oldest drops off when yet another one opens the report.
- This browser can no longer open report on a card means the report was deleted, or it was opened on several other devices since. If it still exists, look it up again with the reference and your email.
- Lookups are limited to stop guessing. After a few wrong tries for one reference, further lookups for it are refused until the next day, so check both fields before you try again.
- One browser follows up to 20 reports; the oldest drop off its list.
Limits and privacy
- A few reports at a time. The form accepts only a few reports per hour and per day from one connection, and tells you when to try again. One complete report is more useful than several short ones.
- No IP address on file. Reports keep a keyed hash of your IP address to limit spam, not the address itself.
- Deleted 90 days after resolution. A report, its files and the record of emails about it are deleted automatically 90 days after it is resolved, or sooner if you ask. The privacy policy explains how to ask.
- Other questions. For anything that isn't a problem with a server or this site, the contact page lists the ways to reach us.
Reports cover problems with our servers and with this site. Use a tunnel only on networks you are allowed to use, as our acceptable use policy asks.





