MacOS Ventura public beta 3 Apple profile
Hi ! Does anyone encounter the problem that the NextDNS profile is configured but is inactive and even switching it to active, the system disable it some minutes after ?
NB : I don't know if it works on Monterey because I always used Ventura since I configured NextDNS.
10 replies
-
I'm on beta 11 and I'm not only unable to toggle the profile from `Inactive` to `Active` but I can't delete it either.
-
Now that MacOS 13 is GA, I tried to use a profile and same it did not seem to be working at all. I previously had the AppStore install removed it, added the profile and was not seeing any device based filtering. I removed the profile added the AppStore install back and it worked fine. I cannot remove the filter either, but has anyone gotten the profile based method to work in MacOS 13?
The app still works but uses the "VPN" method still.
-
This isn't specific to Ventura.
You can only use 1 active network filter at a time. That means you have to decide between using firewall apps, like Little Snitch, Radio Silence and LuLu, or the DNS profile.
If you deactivate the firewall profile, the NextDNS profile will activate just fine.
Also mentioned here and listed by NextDNS as a known issue here a year ago (content filter extension conflict).
I know from a Twitter convo that a network dev from Apple working on these features actually saw the known issue page from NextDNS and mentioned that these issues "might" be the intended behavior, so I wouldn't hold my breath. Apple just doesn't fix most bugs any more or considers them a feature.
I reported the issue to Apple in the summer of 2021: FB9465559
No one else seems to have done so since then.
-
Interesting thanks. I did remove all filter except the Next DNS one and while it's "active" it is not actually passing traffic based on test.nextdns.io
VPN Tracker 365 is an actual VPN and the Appstore VPN was even removed. So the profile shows active but based on the test page it's un-configured...so still not sure of this is a NextDNS or Apple issue, but only using the AppStore version seems to be consistent (or CLI)
Firewall is also inactive so this is as basic as it gets and still no dice with the test URL
{ "status": "unconfigured", "resolver": "141.207.147.254", "srcIP": "174.212.111.186", "server": "vultr-atl-1" }
-
Worth a try but private relay is t enabled and the test page was same in chrome and love logs showed nothing from the named device either. Tried that too. I can try the other free profile but seems odd the nextdns one just doesn’t work at all. For the record the iOS profiles work great on iOS and iPadOS
I am wondering if even after removing the AppStore app and it’s related VPN if something is still there stopping the profile filter but it’s hard to say.
my concern is if the support for the AppStore version starts to lack and profiles are the only way. I’m a paid user so possible I can open a case too. -
Yeah I’ll try that. The only thing could be the actual VPN installed that’s Messi g with it but I need that for remote access to other places so if that’s the case I’d default to the AppStore version but we’d know the issue if that’s it
-
Thanks, well then I guess I have to continue using the VPN client :(
Content aside
-
1
Likes
- 2 yrs agoLast active
- 10Replies
- 349Views
-
6
Following