Skip to content

Network tools

Since v0.17.1 you can debug the network from where your app actually runs: a server’s host network, or the network namespace of a site’s or database’s container. Output streams live. The tools only read: nothing here changes traffic.

The Network tools dialog of a site: server picker, the Ping, Traceroute, DNS, HTTP and TCP tabs, and the fields of the chosen tool.

Tool Does Options
ping Echo requests count 1–20 (default 4)
traceroute The route to a host (traceroute, else mtr, else tracepath) max hops 1–30 (default 20)
dns A lookup with the resolver there type A, AAAA, CNAME, MX, TXT, NS, SRV, PTR (default A); an optional nameserver IP
http A request with a timing breakdown (DNS, connect, TLS, first byte, total), headers like curl -v, TLS version, cipher and certificate chain; the body is counted, not printed method GET or HEAD; connect to an IP (test an origin behind Cloudflare); skip certificate verification
tcp Connection attempts to host:port, one line each with the time or the error count 1–10 (default 3)

Every tool stops after its timeout (1–60 s, default 30). Output is capped at 256 KiB.

Target Runs in
Server Its host network
Native site The host network (native sites use it)
Docker site Its newest running container’s network namespace
Compose site The chosen service’s container
Database instance Its container
Function Refused: functions have no network of their own

Inside a container only the network namespace changes, so the image needs none of the tools. Names resolve the way the app resolves them: the container’s DNS settings and hosts file (read from Docker’s host-side copies), so compose service names and extra_hosts work.

The Network tools section of a server’s Network tab: the Ping, Traceroute, DNS, HTTP and TCP tabs with the ping fields.

  • Server: the Network tools section at the bottom of the server’s Network tab.
  • Site: the site panel’s ⋯ → Network tools. Pick the server (sites on several) and the service (compose), choose a tool, fill its fields and click Run. Your last runs for the target can be opened again.
  • Database containers: the CLI and API for now.
  • Admins only by default: permission network.tools. A site or database target also needs sites.view / databases.view.
  • Every run is audited (network.tool_run) with the tool, target and arguments.
  • 10 runs a minute and 2 running at once per user; at most 4 tools at once per server.
  • Arguments are validated on both sides and passed without a shell. http and tcp refuse link-local addresses (169.254.0.0/16, fe80::/10), which covers cloud metadata endpoints.
  • If ping or every traceroute binary is missing, the run says which package to install. Ubuntu ships ping and tracepath.