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
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.
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.
I have discovered a work around. Tailscale manually overwrite /etc/resolv.conf to do dns resolution when it is unable to correctly interface with systemd-resolved. This is the default behavior on most distros bundled with NetworkManager & systemd-resolved. To allow Tailscale to properly communicate, follow the instructions here
System Info
Distro: EndeavourOS
CPU: 8-core AMD Ryzen 7 6800H with Radeon Graphics (-MT MCP-)
speed/min/max: 503/400/4785 MHz
Kernel: 6.10.5-arch1-1 x86_64
What worked?
Still able to ping 1.1.1.1 and access the internet through IP's directly
What did not work?
When using Tailscale with portmaster, I am unable to resolve any DNS queries.
Debug Information:
NJ{"Created":1723998797,"Modified":1723998797,"Expires":1726590797,"Deleted":0}S
executing core/portmaster-core version 1.6.10 on linux amd64
240818 12:33:17.254 ▶ BOF
240818 12:33:17.386 entication:291 ▶ WARN 001 api: denying api access from 127.0.0.1:45742
240818 12:33:18.387 entication:291 ▶ WARN 003 api: denying api access from 127.0.0.1:58746
240818 12:33:19.388 entication:291 ▶ WARN 005 api: denying api access from 127.0.0.1:58762
240818 12:33:20.390 entication:291 ▶ WARN 007 api: denying api access from 127.0.0.1:58768
240818 12:33:21.391 entication:291 ▶ WARN 009 api: denying api access from 127.0.0.1:58776
240818 12:33:22.392 entication:291 ▶ WARN 011 api: denying api access from 127.0.0.1:58790
240818 12:33:23.146 les/worker:109 ▶ ERRO 013 resolver: service-worker ip info delayed cache writer failed (1): could not start database cache (type bbolt): timeout - restarting in 2s
240818 12:33:48.321 pat/module:112 ▶ ERRO 015 compat: self-check #3: dns integration check failed: failed to receive test response: lookup a81429592840200e3b8934c09b3931629b.self-check.portmaster.home.arpa. on 100.100.100.100:53: read udp 100.96.67.87:50287->100.100.100.100:53: i/o timeout
240818 12:33:57.736 e/core/api:118 ▶ WARN 017 core: user requested shutdown via action
240818 12:33:57.837 dules/stop:057 ▶ WARN 019 modules: starting shutdown...
240818 12:34:00.326 ◀ EOF
The text was updated successfully, but these errors were encountered: