CLI
logs
Read the daemon log for a tunnel (by protocol).
tunnelctl logs shows the log file written by a tunnel's daemon — useful for diagnosing a
tunnel that's stale or stuck starting. Pick the protocol + identifier, same as
down.
tunnelctl logs http <slug> [flags]
tunnelctl logs tcp <remote-port> [flags]
tunnelctl logs udp <remote-port> [flags]Examples
tunnelctl logs http myapp # last 100 lines (default)
tunnelctl logs http myapp -n 50 # last 50 lines
tunnelctl logs http myapp -n 0 # the entire log
tunnelctl logs tcp 27017 -f # stream new lines as they arrive| Flag | Default | Description |
|---|---|---|
-n, --tail <n> | 100 | Number of lines to show; 0 means the whole file. |
-f, --follow | off | Stream new log lines as they're written. |
The log captures both the embedded FRP client and tunnelctl daemon output. The file
persists after the daemon exits, so it works for live daemons and for inspecting a recent
failure. It lives at ~/.local/state/tunnelctl/<name>.log (where <name> is the slug for
HTTP, or tcp-<port> / udp-<port> for L4 — path varies by platform, see the
CLI overview).