Rubber-Duckie
commented
1 month ago Open Rubber-Duckie opened 1 month ago
Rubber-Duckie
commented
1 month ago 
github-actions[bot]
commented
1 month ago Hey @Rubber-Duckie, thank you for reporting on a compatibility.
We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there. If you can't find your software in the list, then a good starting point is our guide on How do I make software compatible with Portmaster.
If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues.
github-actions[bot]
commented
1 month ago Hey @Rubber-Duckie, thank you for raising this issue with us.
After a first review we noticed that this does not seem to be a technical issue, but rather a configuration issue or general question about how Portmaster works.
Thus, we invite the community to help with configuration and/or answering this questions.
If you are in a hurry or haven't received an answer, a good place to ask is in our Discord community.
If your problem or question has been resolved or answered, please come back and give an update here for other users encountering the same and then close this issue.
If you are a paying subscriber and want this issue to be checked out by Safing, please send us a message on Discord or via Email with your username and the link to this issue, so we can prioritize accordingly.
Rubber-Duckie
commented
1 month ago This is a application failure exception. I struggle to see how its a feature. Suggesting the UX involves overt application failure messages as part of the "experience" seems very odd. That said, this response seems very boiler plate, very bot like. Suggest a real person takes a look at this?
nero-0
commented
1 month ago The same thing happens to me every time I start Portmaster/its service manually.
Raphty
commented
1 month ago @nero-0 can you please share your debug info as well.
this is is not a but I have heard about yet.
Rubber-Duckie
commented
1 month ago @nero-0 can you please share your debug info as well.
this is is not a but I have heard about yet.
It's very strange. This error is reported during start up, but its transient (few seconds) and then the dashboard does open and the application would appear to function normally. Very odd indeed.
nero-0
commented
1 month ago @nero-0 can you please share your debug info as well.
What happened
Select "open app" from portmaster notifier
Then select start service
Error is shown on screen
Then after a few seconds, the dashboard appears
What did you expect to happen
No errors should be raised
Debug Information
Version 1.6.10
``` Portmaster 1.6.10 built with go1.22.3 (gc -cgo) for windows/amd64 at 2024-05-15T12:03:21Z commit 867d0bca2d71d7247039cf8e6b129580c28be7d6 (clean) at 2024-05-15T09:08:08Z from git@github.com:Safing/portmaster.git Licensed under the GPLv3 license. ```Platform: Microsoft Windows 11 Pro 10.0.22631 Build 22631
``` System: Microsoft Windows 11 Pro windows (Standalone Workstation) 10.0.22631 Build 22631 Kernel: 10.0.22631 Build 22631 x86_64 ```No Module Error
Unexpected Logs
``` 240528 02:50:54.236 entication:291 > WARN 002 api: denying api access from 127.0.0.1:57504 240528 02:50:55.524 v/location:303 > WARN 004 netenv: failed to get IPv4 device location from traceroute: did not receive any actionable ICMP reply 240528 02:50:57.405 olver-mdns:114 > WARN 006 intel(mdns): failed to create udp6 listen multicast socket: listen udp6 [ff02::fb]:5353: setsockopt: not supported by windows 240528 02:51:00.417 ine-status:561 > WARN 008 netenv: dns query check failed: query failed: failed to connect to Cloudflare (dot://cloudflare-dns.com:853#config): dial tcp :50009->1.1.1.2:853: i/o timeout 240528 02:51:14.443 er/resolve:460 > WARN 010 resolver: query to dot://cloudflare-dns.com:853#config failed: query failed: failed to connect to Cloudflare (dot://cloudflare-dns.com:853#config): dial tcp :41390->1.1.1.2:853: i/o timeout 240528 02:51:14.443 ine-status:561 > WARN 012 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: query failed: failed to connect to Cloudflare (dot://cloudflare-dns.com:853#config): dial tcp :41390->1.1.1.2:853: i/o timeout 240528 02:51:22.450 er/resolve:460 > WARN 014 resolver: query to dot://cloudflare-dns.com:853#config failed: query failed: failed to connect to Cloudflare (dot://cloudflare-dns.com:853#config): dial tcp :25987->1.1.1.2:853: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. 240528 02:51:22.450 ine-status:561 > WARN 016 netenv: dns query check failed: all 1 query-compliant resolvers failed, last error: query failed: failed to connect to Cloudflare (dot://cloudflare-dns.com:853#config): dial tcp :25987->1.1.1.2:853: connectex: An attempt was made to access a socket in a way forbidden by its access permissions. 240528 02:51:24.941 er/resolve:316 > WARN 018 resolver: async query for ipv4.am.i.mullvad.net.A failed: device is offine 240528 02:55:18.478 CURRENT TIME ```Status: Online
``` OnlineStatus: Online CaptivePortal: ```SPN: disabled (module disabled)
``` HomeHubID: HomeHubName: HomeHubIP: Transport: --- Client: true PublicHub: false HubHasIPv4: false HubHasIPv6: false ```Resolvers: 3/3
``` 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 192.168.1.1 (dns://192.168.1.1:53#system) dns://192.168.1.1:53#system Failing: false ```Config: 13
``` core/expertiseLevel: user core/metrics/instance: [redacted] dns/nameservers: [redacted] dns/noInsecureProtocols: true dns/useStaleCache: true filter/askTimeout: 300 filter/askWithSystemNotifications: true filter/blockLAN: true filter/defaultAction: ask filter/endpoints: [redacted] filter/lists: [TRAC MAL DECEP BAD BT-META BT-APPL CB-MW WSP DCT OISD-EXTRA UNBREAK] filter/serviceEndpoints: [redacted] spn/enable: false ```Updates: stable (13/33)
``` Active: all/intel/geoip/geoipv4.mmdb.gz: 20231201.0.1 all/intel/geoip/geoipv6.mmdb.gz: 20231201.0.1 all/intel/lists/base.dsdl: 20240501.0.10 all/intel/lists/index.dsd: 2023.6.13 all/intel/lists/intermediate.dsdl: 20240526.0.0 all/intel/lists/urgent.dsdl: 20240527.22.19 all/intel/portmaster/news.yaml: 20240502.16.6 all/intel/portmaster/notifications.yaml: 20231218.17.37 all/ui/modules/assets.zip: 0.3.1 all/ui/modules/portmaster.zip: 0.8.6 windows_amd64/core/portmaster-core.exe: 1.6.10 windows_amd64/kext/portmaster-kext.sys: 1.1.2 windows_amd64/start/portmaster-start.exe: 1.6.0 Selected: all/dashboards/hubs.json: 0.0.2 all/intel/geoip/geoipv4-mini.mmdb.gz: 20231201.0.1 all/intel/geoip/geoipv4.mmdb.gz: 20231201.0.1 all/intel/geoip/geoipv4.mmdb: 20231201.0.1 all/intel/geoip/geoipv6-mini.mmdb.gz: 20231201.0.1 all/intel/geoip/geoipv6.mmdb.gz: 20231201.0.1 all/intel/geoip/geoipv6.mmdb: 20231201.0.1 all/intel/lists/base.dsdl: 20240501.0.10 all/intel/lists/index.dsd: 2023.6.13 all/intel/lists/intermediate.dsdl: 20240526.0.0 all/intel/lists/urgent.dsdl: 20240527.22.19 all/intel/portmaster/news.yaml: 20240502.16.6 all/intel/portmaster/notifications.yaml: 20231218.17.37 all/intel/spn/main-intel.yaml: 20240213.17.8 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.8.6 all/ui/modules/profilemgr.zip: 0.1.7 all/ui/modules/settings.zip: 0.1.8 windows_amd64/app/portmaster-app.zip: 0.2.8 windows_amd64/core/portmaster-core.exe: 1.6.10 windows_amd64/hub/spn-hub.exe: 0.7.7 windows_amd64/jess/jess.exe: 0.3.3 windows_amd64/kext/portmaster-kext.dll: 1.0.14 windows_amd64/kext/portmaster-kext.pdb: 1.1.2 windows_amd64/kext/portmaster-kext.sys: 1.1.2 windows_amd64/notifier/portmaster-notifier.exe: 0.3.6 windows_amd64/notifier/portmaster-snoretoast.exe: 0.6.0 windows_amd64/notifier/portmaster-wintoast.dll: 0.1.4 windows_amd64/packages/portmaster-installer.exe: 1.0.13 windows_amd64/start/portmaster-start.exe: 1.6.0 ```