Closed jla3378 closed 3 years ago
Interesting. I never had a problem like this one until UDM updated from 1.7.2 to 1.7.3 automatically. (Should have had that disabled.) Correlation != causation, but it was after this that I began having trouble logging into the UniFi web interface and UniFi mobile app. Was able to temporarily fix the problem with the following:
unifi-os restart
Nope doesn't work although curiously when I look at the logs it seems that when the scripts are running, the UDM sees itself as being on the VLAN (10.1.10.1) that I assigned for DNS whereas when the boot up scripts are not enabled, the UDM reports its system IP as the untagged VLAN (172.24.0.1) Untitled.txt
the workaround that is the least problematic is disabling the on_boot script and manually running each script after it's up and running. I would play around with sleep settings but I don't have time for that now so that'll be for later.
Also is your VLAN 5? Can you paste an ifconfig output?
Also you are on the UniFi Controller 6.0.4. I have not tested any of that with the beta controller. So you are on your own for now. If you fix anything please update the files here!
Also, is it only the DNS script that borks the bootup? Make sure your ipv6 gw has a Subnet associated with it (/64)
Interesting. I never had a problem like this one until UDM updated from 1.7.2 to 1.7.3 automatically. (Should have had that disabled.) Correlation != causation, but it was after this that I began having trouble logging into the UniFi web interface and UniFi mobile app. Was able to temporarily fix the problem with the following:
- ssh to UDM as root
- Run
unifi-os restart
Just updated my UDM firmware to 1.8_rc7 with network controller 5.14.18 and stability/access issues seem to be gone. Feeling reckless tonight, so I'm going to bump the network controller to 6.0.4 next.
@SturdyErde There seems to be a bug in the 6.0.4 controller with the Unifi dnsfilter. At least me and one other person have a problem with it. For more information see https://github.com/boostchicken/udm-utilities/issues/28
It would be interesting to know if you’re having the same problems after the update.
I've been too busy lately to work on this, but yes, it does seem to be a global problem with the 6.0.4 controller. I guess that's what we get for installing beta, especially when it's tagged 'unstable'!
Closing since it was a beta issue
20-dnsipv6.conflist.txt 11-dns.sh.txt
I've uploaded my config files and script minus my ipv6 address.
I'm running a nextdns container and it works great except that for some reason when I enable the boot scripts, the web interface of the UDM doesn't run at all. I tried using 1.7.2 and the latest 1.8.0. I confirmed using ss that the process that normally listens to 443 no longer does so.
Every time I want to make a change I have to disable the scripts, reboot, make the changes, reenable the script, and reboot again.