1

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

null
    • Daniel_Sieradski
    • 2 yrs ago
    • Reported - view

    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.

     

     

    • Chris_Colotti
    • 2 yrs ago
    • Reported - view

    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.

    • Chris.6
    • 2 yrs ago
    • Reported - view

    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.

    • Chris_Colotti
    • 2 yrs ago
    • Reported - view

    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"
}
      • Chris.6
      • 2 yrs ago
      • Reported - view

      Chris Colotti I see, that might actually be something else then. I only know that the network filter (1 at a time) issue isn't new and it seems that both OP and the other user in this thread can't use the profile because they use an active content filter from the firewall apps.

      To further isolate if your problem is the fault of macOS or NextDNS, you could try installing the profile from Adguard (free to try) and see if that works. 

      Also, make sure to look at your logs (live) while browsing. If things show up, it works. The NextDNS test page doesn't work with Safari and Private Relay enabled, but filtering still happens (with some caveats). 

    • Chris_Colotti
    • 2 yrs ago
    • Reported - view

    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. 

      • Chris.6
      • 2 yrs ago
      • Reported - view

      Chris Colotti At this point I think testing the Adguard profile is the best option left for troubleshooting to see if it's a Ventura or NextDNS issue. 

      I'm on Monterey and have both the NextDNS app and profile installed. I've never uninstalled the app to run the profile. I just disable the connection in the app (not even quitting the app) and enable the profile. As long as I inactivate the other network filter (Little Snitch in my case) it works. So at least in Monterey, the profile and app coexist peacefully.

      If it were me, I'd try the Adguard profile first and only then uninstall the NextDNS app / other VPN apps to see if that makes a difference. 

    • Chris_Colotti
    • 2 yrs ago
    • Reported - view

    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 

    • puchijon
    • 2 yrs ago
    • Reported - view

    Thanks, well then I guess I have to continue using the VPN client :(

      • Chris.6
      • 2 yrs ago
      • Reported - view

      Johnny BOI You can use both by using the NextDNS app instead of the NextDNS profile. The limitation of only 1 active network content filter doesn't apply when using the NextDNS app. I use it together with the Little Snitch firewall.

Login to reply

Content aside

  • 1 Likes
  • 2 yrs agoLast active
  • 10Replies
  • 346Views
  • 6 Following