The easiest way to find your debug info is to follow this guide: FAQ Debug Info
If copied like described above, each section starts with <details> and ends with </details> , this is so that GitHub will interoperate those section in a format where each can be collapsed and expanded separately.
Note that in the logs you will find entries labeled [redacted] . The entries are redacted automatically because there could be sensitive information in them. The reason there is an entry is to let the reader know that there has been a change/configuration made by the user.
Overview
Very basic information
Errors and unexpected logs
Network connection information [only in per app Debug Info]
Status information from various modules
Detailed information
This section gives basic information about which Portmaster Core you are running.
<details>
<summary>Version 1.0.13</summary>
```
Portmaster
version 1.0.13
commit tags/v1.0.13-0-g368ce6e03132631b37d1c2ead0e37f21f7bae905
built with go1.20 (gc) linux/amd64
using options main.go
by user@docker
on 25.04.2023
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
```
</details>
Gives context to what Operating System and Kernel version Portmaster is running on.
<details>
<summary>Platform: fedora 38</summary>
```
System: fedora linux (fedora) 38
Kernel: 6.2.14-300.fc38.x86_64 x86_64
```
</details>This displays when there is a module error, and will be empty most of the time. It has more importance for the developers. So don't worry, if its empty.
As the name implies, here you should find the logs associated with the issues you experience.
This typically is the place to start looking if something isn't working.
230508 14:31:27.699 er/resolve:445 ▶ WARN 070 resolver: query to dot://cloudflare-dns.com:853#config failed: query failedHere you can see that Portmaster had issues connecting to cloudflare DNS. This will result in not being able to resolve domains thereby feeling like you don't have internet. Your Device just does not know where to go/connect to online.
This only shows up on a per app Debug Info, not the global one.
<details>
<summary>Network: 33/33 [~0] Connections</summary>
```
ProfileName: Brave
Profile: e33bf29f-96d4-41d4-961d-8855c40c7c92
Source: local
ProcessName: brave
BinaryPath: /app/brave/brave
CmdLine: /app/brave/brave --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --crashpad-handler-pid=17 --enable-crash-reporter=,unknown --change-stack-guard-on-fork=enable --shared-files=v8_context_snapshot_data:100 --field-trial-handle=0,i,12378382202494345037,4650447694201746411,262144 --disable-features=DesktopPWAsRunOnOsLogin,WebAssemblyTrapHandler
PID: 6202
tunneled 10.x.x.x:51456 TCP> 151.x.x.x:443 08:13:08- P#6202 [ETM] allowed by default action - by filter/defaultAction @ global
…
…
…
```
</details>This Section has not been updated in a while and mainly shows some high level Status information - we will be making this section more useful in the future.
<details>
<summary>Status: Trusted</summary>
```
ActiveSecurityLevel: Trusted
SelectedSecurityLevel: Off
ThreatMitigationLevel: Trusted
CaptivePortal:
OnlineStatus: Online
```
</details>
This section displays the information Portmaster has about the SPN.
<details>
<summary>SPN: connected (module enabled)</summary>
```
HomeHubID: xxx
HomeHubName: xxx
HomeHubIP: x.x.x.x
Transport: tcp:17
Connected: 2h47m0s ago
---
Client: true
PublicHub: false
HubHasIPv4: false
HubHasIPv6: false
---
Map main:
Active Terminals: 11 Hubs
State Active: 48 Hubs
State ConnectivityIssues: 4 Hubs
State HasRequiredInfo: 34 Hubs
State IsHomeHub: 1 Hubs
State Reachable: 48 Hubs
State Trusted: 36 Hubs
State UsageAsHomeDiscouraged: 16 Hubs
```
</details>This is a list of all the DNS server Portmaster has. They are in the order Portmaster would use them, top to bottom. The #configured are the ones setup from within Portmaster and the #system are the ones from the Operating System Portmaster sees and would fall back to. This fall back behavior is the default and can be changed in the global settings.
<details>
<summary>Resolvers: 4/4</summary>
```
Cloudflare (dot://cloudflare-dns.com:853#config)
dot://cloudflare-dns.com:853#config
Failing: false
Cloudflare (dot://cloudflare-dns.com:853#config)
dot://cloudflare-dns.com:853#config
Failing: false
10.117.0.1 (dns://10.117.0.1:53#system)
dns://10.117.0.1:53#system
Failing: false
1.1.1.1 (dns://1.1.1.1:53#system)
dns://1.1.1.1:53#system
Failing: false
```
</details>As the name implies, this is a list of the user changed global settings.
<details>
<summary>Config: 4</summary>
```
core/metrics/push: [redacted]
core/releaseChannel: beta
dns/useStaleCache: true
spn/enable: true
```
</details>
Here you see the release channel Portmaster uses, as well as the version number of each module.
<details>
<summary>Updates: beta (13/26)</summary>
```
Active:
all/intel/geoip/geoipv4.mmdb.gz: 20230102.9.32
all/intel/geoip/geoipv6.mmdb.gz: 20230102.13.14
all/intel/lists/base.dsdl: 20230501.0.5
all/intel/lists/index.dsd: 2023.4.6
all/intel/lists/intermediate.dsdl: 20230507.0.0
all/intel/lists/urgent.dsdl: 20230509.3.1
all/intel/portmaster/notifications.yaml: 20230406.14.51
all/intel/spn/main-intel.yaml: 20230405.9.59
all/ui/modules/assets.zip: 0.3.1
all/ui/modules/portmaster.zip: 0.4.6
linux_amd64/app/portmaster-app.zip: 0.2.5
linux_amd64/core/portmaster-core: 1.0.13
linux_amd64/start/portmaster-start: 1.0.13
Selected:
all/dashboards/hubs.json: 0.0.2
all/intel/geoip/geoipv4.mmdb.gz: 20230102.9.32
all/intel/geoip/geoipv4.mmdb: 20230102.9.32
all/intel/geoip/geoipv6.mmdb.gz: 20230102.13.14
all/intel/geoip/geoipv6.mmdb: 20230102.13.14
all/intel/lists/base.dsdl: 20230501.0.5
all/intel/lists/index.dsd: 2023.4.6
all/intel/lists/intermediate.dsdl: 20230507.0.0
all/intel/lists/urgent.dsdl: 20230509.3.1
all/intel/portmaster/notifications.yaml: 20230406.14.51
all/intel/spn/main-intel.yaml: 20230405.9.59
all/ui/modules/assets.zip: 0.3.1
all/ui/modules/base.zip: 0.2.11
all/ui/modules/console.zip: 0.1.11
all/ui/modules/monitor.zip: 0.2.4
all/ui/modules/portmaster.zip: 0.4.6
all/ui/modules/profilemgr.zip: 0.1.7
all/ui/modules/settings.zip: 0.1.8
linux_amd64/app/portmaster-app.zip: 0.2.5
linux_amd64/core/portmaster-core: 1.0.13
linux_amd64/hub/spn-hub: 0.6.6
linux_amd64/jess/jess: 0.3.1
linux_amd64/notifier/portmaster-notifier: 0.3.5
linux_amd64/packages/portmaster-installer.deb: 1.0.0
linux_amd64/packages/portmaster-installer.rpm: 1.0.0
linux_amd64/start/portmaster-start: 1.0.13
```
</details>This looks very different depending on the Operating System.
On Windows you will see: all registered WFP drivers (excluding common ones)
On Linux you will see: the IPTables Chain
This displays the internal state of Portmaster programming. It contains no private information and is meant for developers.