You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Portmaster UI - Dashboard - Features section - tiles for Safing Support and Bandwidth Visibility have no function.
What did you expect to happen?:
I am pretty sure that these two tiles used to be clickable. Safing Support opened a page with links to all support options. Bandwith Visibility opened some charts with bandwidth overview per app, row by row, I believe.
How did you reproduce it?:
These two tiles are dead on every start of Portmaster. They had function in the past. The other four main tiles in this section work as expected.
Debug Information:
Version 1.6.5
Portmaster
version 1.6.5
commit tags/v1.6.5-0-ge9940d77a01f32cc11d3ed70e19482bdea773fc5
built with go1.21.2 (gc) windows/amd64
using options
by user@docker
on 11.01.2024
Licensed under the AGPLv3 license.
The source code is available here: https://github.com/safing/portmaster
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
System: Microsoft Windows 10 Pro windows (Standalone Workstation) 10.0.19045 Build 19045
Kernel: 10.0.19045 Build 19045 x86_64
No Module ErrorUnexpected Logs
240426 08:16:25.590 /operation:245 > WARN 408 spn/terminal: operation connect a7a8e5#8#0>32 failed: [ext] connection error
240426 08:21:32.279 /operation:245 > WARN 410 spn/terminal: operation connect a7a8e5#8#0>40 failed: [ext] connection error
240426 08:25:20.968 /operation:245 > WARN 412 spn/terminal: operation connect a7a8e5#8#0>48 failed: [ext] connection error
240426 08:26:22.977 le/profile:519 > WARN 414 profile: failed to get binary icon/name for C:\Users\...\AppData\Local\Discord\app-1.0.9043\Discord.exe: failed to convert ico to png: failed to decode ICO: unexpected EOF
240426 08:26:29.663 /operation:245 > WARN 416 spn/terminal: operation connect a7a8e5#8#0>64 failed: [ext] connection error
240426 08:27:26.971 /operation:245 > WARN 418 spn/terminal: operation connect a7a8e5#8#0>88 failed: [ext] connection error
240426 08:30:57.513 ew/connect:363 > WARN 420 spn/crew: reachability check to <Hub nonornia Qyqh-VZf7> timed out
240426 08:31:13.628 er/resolve:460 > WARN 422 resolver: query to dot://cloudflare-dns.com:853#config failed: query failed
240426 08:49:44.757 /operation:245 > WARN 424 spn/terminal: operation connect a7a8e5#8#0>1016 failed: connection error: failed to read from origin: read tcp4 192.168.1.107:717->192.168.1.107:61500: wsarecv: An existing connection was forcibly closed by the remote host.
240426 08:51:56.771 er/resolve:460 > WARN 426 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 :60619->1.1.1.2:853: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
240426 09:20:40.183 CURRENT TIME
Status: Online
OnlineStatus: Online
CaptivePortal:
SPN: connected (module enabled)
HomeHubID: Zwvq7fgGuwWM14qStngZK2Z2q94fdHwr9SumtsJ9yufMPr
HomeHubName: lonelak
HomeHubIP: 91.236.230.76
Transport: http:80
Connected: 1h14m0s ago
---
Client: true
PublicHub: false
HubHasIPv4: false
HubHasIPv6: false
---
Map main:
Active Terminals: 2 Hubs
State Active: 62 Hubs
State AllowUnencrypted: 32 Hubs
State ConnectivityIssues: 1 Hubs
State HasRequiredInfo: 36 Hubs
State IsHomeHub: 1 Hubs
State Reachable: 62 Hubs
State Superseded: 5 Hubs
State Trusted: 31 Hubs
State UsageAsHomeDiscouraged: 37 Hubs
DatagramV4Callout Callout This callout is used to handle datagram data for IPv4. {a6be3096-66bf-4959-8629-1c3a4c40c31e} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4
DatagramV4Filter Filter The filter is used for handling datagram data for IPv4. {915a8ed4-e7ee-41ca-94a8-0f299c5fe008} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
DatagramV6Callout Callout This callout is used to handle datagram data for IPv6. {d55cb395-29a1-4716-8cb1-65c888995f54} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6
DatagramV6Filter Filter The filter is used for handling datagram data for IPv6. {4463957b-211e-4717-baea-2c46798b44f1} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
Edge traversal Teredo Authorization Sublayer SubLayer Edge traversal Teredo Authorization Sublayer {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
PortmasterALEInboundV4Callout Callout This callout is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {e36216c5-7b33-40ee-b054-fb1bc7decc19} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4
PortmasterALEInboundV4Filter Filter This filter is used by the Portmaster to monitor inbound IPv4 traffic before the connection is established. {1d18d774-1895-4f38-9829-6f6f1f350b9e} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEInboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {77ea9927-66e7-4cf8-9ea2-941edf2fae63} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6
PortmasterALEInboundV6Filter Filter This filter is used by the Portmaster to monitor inbound IPv6 traffic before the connection is established. {a27d9faf-c109-4d68-aed8-0bdcc18ebdbd} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV4Callout Callout This callout is used by the Portmaster to montiror outbound IPv4 traffic before the connection is established. {029819fe-97d9-4e5f-a0fb-78ef5cef8ac4} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4
PortmasterALEOutboundV4Filter Filter This filter is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {728ae7ec-9da2-48bc-bf3f-688c074b3700} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {d6b0213a-337a-4cc6-84c0-cc60731b9e2a} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6
PortmasterALEOutboundV6Filter Filter This filter is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {120b5015-206f-47a3-bc5d-2afafca9cd23} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV4Callout Callout This callout is used by the Portmaster to intercept inbound IPv4 traffic. {05c55149-4732-4857-8d10-f178f3a06f8c} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4
PortmasterInboundV4Filter Filter This filter is used by the Portmaster to intercept inbound IPv4 traffic. {6cfb97bd-a2a2-4166-ae71-bc34c115e7ed} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV6Callout Callout This callout is used by the Portmaster to intercept inbound IPv6 traffic. {ceff1df7-2baa-44c5-a6e5-73a95849bcff} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
PortmasterInboundV6Filter Filter This filter is used by the Portmaster to intercept inbound IPv6 traffic. {c4799a47-cc1e-4f80-be79-3e18fc16eddd} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV4Callout Callout This callout is used by the Portmaster to intercept outbound IPv4 traffic. {41162b9e-8473-4b88-a5eb-04cf1d276b06} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
PortmasterOutboundV4Filter Filter This filter is used by the Portmaster to intercept outbound IPv4 traffic. {793caf85-9057-4d4d-a42d-a4cfcedaa87d} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV6Callout Callout This callout is used by the Portmaster to intercept outbound IPv6 traffic. {32bad112-6af4-4109-809b-c07570ba01b4} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6
PortmasterOutboundV6Filter Filter This filter is used by the Portmaster to intercept outbound IPv6 traffic. {8e6d76b2-e87b-42ad-8a1a-b906bb57906c} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterSublayer SubLayer The Portmaster sublayer holds all it's filters. {a87fb472-fc68-4805-8559-c6ae774773e0}
StreamV4Callout Callout This callout is used to handle stream data for IPv4. {525dac52-65de-4a6f-b546-2b1f3bc226db} [no provider key] FWPM_LAYER_STREAM_V4
StreamV4Filter Filter The filter is used for handling stream data for IPv4. {5fabd434-da0b-4a32-8f1b-b2a732a28c68} [no provider key] FWPM_LAYER_STREAM_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
StreamV6Callout Callout This callout is used to handle stream data for IPv6. {4321ddf9-57b2-4391-8fc5-c5b46c655587} [no provider key] FWPM_LAYER_STREAM_V6
StreamV6Filter Filter The filter is used for handling stream data for IPv6. {99893688-3ab6-49f6-ac58-5e10e4f1139d} [no provider key] FWPM_LAYER_STREAM_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
Surfshark Provider [no description] {e02aa731-91c8-4f52-ab21-770fe1536f72}
Surfshark Split tunnel sublayer SubLayer [no description] {e02aa731-91c8-4f52-5375-624c61796572}
Teredo socket option opt out block filter Filter [no description] {56a0cbf3-dced-4de6-b3ef-815b7cf8d475} {75c0bf46-fe90-4bbe-9f83-b22993434d83} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
Closing this ticket, as the "Help" button on the left vertical does the same. I thought it would jump there from the Features tile. Maybe I am mistaken. Now I am also not sure about the "Bandwidth" tile anymore.
Ignore this ticket for now.
Pre-Submit Checklist:
What happened:
Portmaster UI - Dashboard - Features section - tiles for Safing Support and Bandwidth Visibility have no function.
What did you expect to happen?:
I am pretty sure that these two tiles used to be clickable. Safing Support opened a page with links to all support options. Bandwith Visibility opened some charts with bandwidth overview per app, row by row, I believe.
How did you reproduce it?:
These two tiles are dead on every start of Portmaster. They had function in the past. The other four main tiles in this section work as expected.
Debug Information:
Version 1.6.5
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
No Module Error
Unexpected Logs
Status: Online
SPN: connected (module enabled)
Resolvers: 4/4
Config: 12
Updates: stable (14/33)
Compatibility: WFP State (29)
Goroutine Stack
The text was updated successfully, but these errors were encountered: