Report a Problem
Where SwiftServer keeps its diagnostics, and what to include so we can fix your issue in one reply.
Almost every problem is diagnosable from information SwiftServer already collected. This page shows where that information lives, and what to send to [email protected] — or share in the Telegram group — so most reports become one-reply fixes.
Where the diagnostics live
Any failed connection — dashboard status, terminal, SFTP, port forwarding, Docker: open the failure dialog and you'll find an Event Log (what happened, step by step) and SSH Diagnostics (the protocol-level detail). Both are copyable text.
Terminal behavior problems (rendering, input, disconnects) — enable Settings → Terminal → Terminal Debug Logs, reproduce the issue, and use Copy to grab the log. It records runtime events only — never your terminal contents, selections, or clipboard.
Mosh — the disconnect dialog has a dedicated Mosh Diagnostics section with the full bootstrap and connection log.
Monitoring data problems (a card missing, values blank or wrong) — the fastest diagnosis is running the same command SwiftServer runs and sending the output; the per-platform commands are listed in Monitoring issues.
Docker panel — the panel names the failure precisely; see Docker issues for fixes and what to send.
Everything else — Settings → Support → View Recent Logs is the app-wide log viewer, filterable by category (Dashboard, Terminal, SFTP, Docker, Widget, …), level, and machine, with a Copy button for exactly the lines you filtered.
The fast path
Settings → Support → Feedback opens a pre-addressed email that already includes your app version, build, and OS version — paste the diagnostics in and send. Join Telegram Group in the same section reaches the community directly.
A good report includes
- What you did and what you expected — one or two sentences.
- App version and platform — e.g. "2.0.5 on iPhone", from Settings.
- Server OS — Linux distribution, macOS, or Windows.
- The diagnostics text from the sections above, pasted or screenshotted.
We read every report. If something in these docs was the problem, telling us that helps too — the docs get fixed the same way the app does.