Beta Claims: Detected Compatibility Issue ... Won't tell me what the issue is

[Alex9001]

Artix w/ KDE Plasma. Openrc. Using Portmaster-stub with portmaster-openrc package. When using Beta after a few minutes it claims to have an incompatibility issue.

I don't have anything running that would cause a problem. I don't even have firewalld or ufw installed. And I removed clamtk portmaster is still mad.

Here are the processes I have running: https://pastebin.com/HY1mYa6e

Its just a bunch of plasma stuff.

Debug Information:

[github-actions[bot]]

Hey @Alex9001, 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.

[Alex9001]

Ok, this probably has to do with DNSMASQ

Some beta update came out. Noticed portmaster was off. When I tried to start it it was complaining 127.0.0.17:53: bind: address already in use

I did

sudo ss -tulpn | grep 53
udp   UNCONN 0      0               [::]:53            [::]:*    users:(("dnsmasq",pid=3650,fd=6))          
tcp   LISTEN 0      32           0.0.0.0:53         0.0.0.0:*    users:(("dnsmasq",pid=3650,fd=5))          
tcp   LISTEN 0      32              [::]:53            [::]:*    users:(("dnsmasq",pid=3650,fd=7))        

sudo rc-service dnsmasq stop
sudo rc-service portmaster stop
sudo rc-service portmaster start

Now it stopped complaining.

I'm not leet enough to figure out a solution.

But I need DNSMASQ for qemu virtual machines.

[Alex9001]

Never mind it is not DNSMASQ. Even with service stopped it still complains about compatibility issue. And I moved DNS listening address in portmaster to 127.0.0.17:53 as per another issue so it shouldn't be a problem

How can I tell why portmaster is complaining?

[Alex9001]

Ok looks like its only complaining when I use system DNS servers... which go to AdGuard Home on 192.168.1.1:53 that's running on my router. Then AdGuard sends those DNS queries to Unbound which then sends DOT queries upstream.

I know there's a compatibility workaround for Adguard on #431 , however this is Adguard Home which is running on a completely different machine and not the same thing.

[e-t-l]

Possibly related to this, at least tangentially: On the old Stable build, when there's a Detected Compatibility Issue, the (Windows) tray icon would have a red dot, indicating that if you open the PM gui there will be an unhappy red shield symbol. Currently, even when there is a compatibility issue that produces the in-app red shield status, the tray icon still has a green dot. This makes the tray icon pretty useless, as it is no longer a reliable indicator of PM's status.

[Alex9001]

This happens in V2 stable

Every address i have tried gives me a bind error

Secure DNS Error

The internal DNS server failed. Restart Portmaster to try again. Error: listen udp 127.0.0.17:53: bind: address already in use

[github-actions[bot]]

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

[Alex9001]

still happening all latest

[Flavelius]

i have this compatibility issue error as well since upgrading to V2. I uninstalled V1 and did a fresh V2 install. I don't use adguard or any other dns/filter/firewall software. I only have a custom dns set in my router. After portmaster starts at some point, maybe 30s in, i cannot access the internet anymore, shutting down/uninstalling fixes it.

Ubuntu 24.04

Edit: i downgraded, V1 still works fine for me.