3

Issue with latest Ubiquiti Unifi UDM Pro

Upgraded my UDM this morning to Device Version 4.0.21.  I now see the below issue.  I was running on a previous version of UDM Pro yesterday and re-installed NextDNS and it was fine. It wasn't until I upgraded my UDM Pro this morning and re-installed NextDNS again that this issue started.

 

After several minutes, I get this error: 

 

One of my buddies is also running into this problem with his UDM Pro and will send him this link.

12 replies

null
    • ryan_k
    • 2 mths ago
    • Reported - view

    I had the same issue start last night on an older version. It worked for a few hours after re-running the installer. I checked this morning, and I was in an error state again. I upgraded to 4.0.21 but I'm still in an error state after running the NextDNS installer. 

    • Craig.7
    • 2 mths ago
    • Reported - view

    Exactly the same issue here.

    • Brad_Kowal
    • 2 mths ago
    • Reported - view

    Ya something broke on NextDNS side with code is what it looks like to me..although I just did an upgrade to release candidate 4.0.21 which could be it also..but...

    I'm only able to specify one ID versus the usual two I have running. Here's my normal config I've been running for years that have to execute after a UDM upgrade. 

    nextdns config set \
    -profile 192.168.200.1/24=49899a \
    -profile 40:a2:db:16:17:97=49899a \
    -profile d4:68:aa:25:1f:82=49899a \
    -profile 74:04:F1:59:72:1B=49899a \
    -profile 646cd6
    nextdns restart

     

    I can get all traffic going to on ID on NextDNS but not split like it was. Something broke just not sure where...

    • Eric.9
    • 2 mths ago
    • Reported - view

    Are you all using the CLI?

    • Brad_Kowal
    • 2 mths ago
    • Reported - view

    Yup always 

    • Elan_Shudnow
    • 2 mths ago
    • Reported - view

    Yes, using the CLI.

    • ryan_k
    • 2 mths ago
    • Reported - view

    Yes, I was using CLI. I switched to setting Linked IP with my UDMP. It seems to be intermittently working. The health check on the setup page seems to round robin between success and errors. 

    • Elan_Shudnow
    • 1 mth ago
    • Reported - view

    For me, I tried what Ryan said and it still doesn't work for me 100% of the time.  NextDNS integration is essentially completely broken.

    • Elan_Shudnow
    • 1 mth ago
    • Reported - view

    I have a Synology at home so tried shifting away from my clients using DNS on my UDM Pro by installing NextDNS on my Synology and updating DHCP for clients to talk through my Synology for DNS.  Same exact problem.  Strange, not sure what is going on regardless if NextDNS is being handled by Synology or my UDM Pro.

      • Brad_Kowal
      • 1 mth ago
      • Reported - view

       yep that’s a good anlter option. If you wanna keep using nextDNS services, I agree.

      • ryan_k
      • 1 mth ago
      • Reported - view

       Except it isn't working either. 

    • Elan_Shudnow
    • 1 mth ago
    • Reported - view

    Looks like everything is working again with my UDMP.  Must have been an issue with the NextDNS Service itself that coincidently occurred after upgrading my UDMP.  This would explain why others had the issue even with older versions of UDMP.

Login to reply

Content aside

  • 3 Likes
  • 1 mth agoLast active
  • 12Replies
  • 413Views
  • 6 Following