Reporting a Bug

What to check first, how to collect logs and diagnostics, and what to put in the issue.

Report bugs on GitHub:

Throne desktop: github.com/throneproj/Throne/issues
Throne for Android: github.com/throneproj/ThroneForAndroid/issues

For questions about using Throne desktop, use the Q&A category of GitHub Discussions instead.

Before you report

Update Throne with Program → Check For Update, or from the downloads page.
Search the open and closed issues for your error message, and read the FAQ and Troubleshooting.
Test with a fresh configuration that has only what shows the problem, and say in the report whether the problem happens there too.
If you use a WinGet, Scoop, AUR or Nix package, test the official build too; the developers do not support these packages.
If only one server fails, test it in another app. If it fails there too, contact your provider.

Collect logs

Desktop

The Logs tab at the bottom of the main window shows the log, and Throne writes the same lines to logs/throne.log in the config folder (Settings → Open Config Folder). The file starts again every time Throne starts, so copy it before you restart.

To record a detailed log:

In Settings → Basic Settings → Logging (Advanced mode only, see Simple and Advanced mode), set Sing-box Log level to debug, and for Xray profiles also Xray Log level.
Raise Max log lines, for example to 2000, so that Throne does not drop log lines.
Click OK and restart Throne with Program → Restart Program.
Reproduce the problem and attach logs/throne.log. If you copy from the Logs tab instead, close its filter bar first.
Set the log levels back to info (sing-box) and warning (Xray).

After a crash, attach logs/crashed-<date>-<time>.log, and on Windows the .txt and .dmp files from the crashes folder.

Android

Open the drawer and tap Logs. Keep Hide sensitive data on (the default), then tap Share logs or Save logs…. For a detailed log, first set Settings → Core → Log level to debug (and Xray log level for Xray profiles). See Android Troubleshooting.

Diagnostics

For freezes, hangs and high CPU use, the developers may ask for a Diagnostics file, a 30-second recording of what the core does.

Bring Throne into the state with the problem, for example wait until it hangs. Do not restart Throne.
In Settings → Basic Settings → Diagnostics, tick the options the developer asked for: Lock contention, Execution trace (larger file) or Include Throne logs.
Click Start and wait 30 seconds. Start works only while the core runs.
Click Show in folder and attach the throne-profile-<date>-<time>.zip file.

The file lists your Throne version, system and a few settings, but none of your configs. Include Throne logs adds your logs, which contain visited domains and server addresses. On Android, use Settings → Diagnostics; see Diagnostics.

What to include

Use the issue template and fill in every field:

Item	Where to find it
Throne version	`Program` → `About`, which lets you copy all component versions. On Android: `About`.
Installation type	ZIP, Windows installer, `.deb`, `.rpm`, install script, repository or package manager, and whether you use headless Throne.
Mode	`Tun Mode`, `System Proxy` or both, and whether the kill switch is on.
Profile type	The `Type` column, for example `VLESS (Xray)`. Not the link.

For routing problems, use the Routing Issue template and add your routing profile: in Settings → Routing Settings → Route, select it and click Export to copy a throne://route/… link. Check it for private domains and addresses first.

If a developer asks for your configuration, right-click the profile → Share → Export config (Advanced mode only) and copy the sing-box tab, or the Xray tab if asked. Replace passwords, UUIDs, keys and server addresses with xxxx first.

For headless Throne, see also What to include in a bug report.