Debug
Inspect running configuration JSON for support-guided diagnosis.
Debug is the last Misc row. It loads Tunna's running configuration JSON for support-guided diagnosis. It is not a normal editing surface and should not be used to invent node or rule values.
Debug interface
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
Visible choices
These are controls, states, or measurements in the view. Read them as reference, not as feature claims.
Running Configuration
The page shows a Root JSON row. Root starts collapsed.
Expand rows
Tap object or array rows to expand them. Object keys are sorted, and array rows are shown as indexes.
Copy
Long-press an object or array row to copy that JSON subtree. Redact secrets before sharing copied output.
Load errors
Configuration Not Found, Configuration Parse Failed, and Configuration Load Failed are support facts. Mention which one appeared.
Practical Debug uses
Confirm the generated shape
Expand Root when support asks whether the running config contains an expected outbound, routing rule, or protocol section.
Good fit The app can start far enough to write a running config.
Not ideal You are trying to edit settings; Debug is read-only.
Copy only the needed subtree
Long-press the smallest object or array support requested instead of copying the whole Root.
Good fit Support needs one section, such as an outbound or routing object.
Not ideal You have not reviewed the copied JSON for secrets.
Report load failures plainly
If Debug reports Configuration Not Found, Configuration Parse Failed, or Configuration Load Failed, send that exact state after redacting any surrounding details.
Good fit The JSON viewer cannot show the expected configuration.
Not ideal You are guessing which setting caused the failure without a clean log.
Debug can expose secrets
Running configuration can contain node addresses, UUIDs, passwords, Reality keys, subscription-derived values, and rule details. Tunna does not promise automatic redaction for copied JSON. Long-press copy sends the selected JSON subtree to the pasteboard, so review and redact copied output yourself before sharing it with trusted support.