I had originally thought that the issue was caused by hairpin NAT, thus the local record.)Īs of right now these are the Unifi devices I own.
(Note that even without this local record, I had the same problems. set-inform If everything went well the UniFi AP should now be active in the UniFi controller. 10.11.11. There's an public CNAME record set in my DNS provider for, pointing to my DuckDNS hostname, and an A record set on my local DNS server pointing to the same box using its private IP. The UniFi should now show up in the UniFi controller as Pending Adopt it and go back the the Unifi AP and run the above set-inform command again. Adoption failures, saying "managed by another console" when it does finally adopt, you name it. Just bought some Unifi gear for the house, have a self-hosted controller running in an Ubuntu server VM.įor some reason, enabling the "override inform host" option and entering the FQDN of my controller causes the adoption process to freak out. Refer to our UniFi Device LED Status guide to ensure the device is in a factory-default state.
0 kommentar(er)
