Detailed log of all actions performed by the WARP client, including all communication between the device and Cloudflare’s global network. Note: This is the most useful debug log.
Contains detailed DNS logs if Log DNS queries was enabled on WARP.
Date and time (UTC) when you ran the warp-diag command.
Verifies that the WARP DNS servers are set as system default. For operating modes where DNS filtering is enabled, this file contains the IPs of the local WARP DNS proxy (127.0.2.2:0, 127.0.2.3:0, [fd01:db8:1111::2]:0, and [fd01:db8:1111::3]:0).
Statistics on the DNS queries received and resolved by WARP, generated every two minutes.
Static DNS config of device.
macOS console log showing application launch
Log file for the GUI app that users interact with.
The warp-debugging-info folder may contain multiple versions of the same log, such as daemon.log, daemon.1.log, and daemon.2.log. Since logs can get very long, they are rotated either daily or when they exceed a certain size.
<logfile>.log is the most current log. This is almost always the log you should be looking at, as it shows events that occurred on the day you ran the warp-diag command.
<logfile>.1.log shows events from the previous day.
<logfile>.2.log shows events from two days before.