Help
Support.
Pick the app you need help with and write us. Your request goes straight to the right team — we reply by email.
Request
Write to us.
Known issues
Current tickets.
These bugs are reported and not fixed yet. If yours is already on the list, we are on it — no need to report it twice. Titles come straight from the public bug tracker.
NetMute
Awaiting releaseNetMute 2.3.4: DNS proxy beta enabled by default can break name resolutionReported Sep 9, 2026
View ticket on GitHub ↗Affected: NetMute 2.3.4 (build 45 and later)
Symptom: After updating, some Macs lose network access for apps that rely on the system resolver. Safari stops loading pages entirely, while browsers that bring their own DNS (Chrome, Brave, Edge, Arc) and most other traffic keep working. Removing the NetMute network filters in System Settings restores it immediately.
Cause: 2.3.4 enabled the beta option "Check addresses before your Mac reaches them" by default. It installs a second network configuration, a DNS proxy, that sits in front of every name lookup on the Mac. On machines that already run another DNS filter or a local resolver of their own, the two get in each other's way and name resolution stops.
Workaround: Open NetMute and switch off "Check addresses before your Mac reaches them" under Tracker Shield. The DNS proxy is removed and the content filter keeps working normally. Nothing else needs to change.
Fix: In the next build the option is off unless you switch it on, an unwanted DNS proxy left over from the update is removed automatically, and the switch moves into Settings next to the other DNS options.