This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| equipment:unifiaclite [2021/01/30 18:00] – dirk | equipment:unifiaclite [2021/03/08 11:25] (current) – [Troubleshooting] dirk | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| * Hostname: unifi.brimble.com | * Hostname: unifi.brimble.com | ||
| ===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
| - | * I had a couple instances where (i guess after playing with PiHole maybe? I dunno) it would get stuck in adopting mode. This post here https:// | + | * I had a couple instances where (i guess after playing with PiHole maybe? I dunno) it would get stuck in adopting mode. This post here https:// |
| + | Want to solve it permanently? | ||
| + | {{: | ||
| If you don't also check the Override inform host with Controller Hostanme/IP box too, nothing changes. | If you don't also check the Override inform host with Controller Hostanme/IP box too, nothing changes. | ||
| - | |||
| - | |||
| Nine times out of ten when APs can't find the controller, your DNS is not pointing unifi to the IP address of the Unifi controller. | Nine times out of ten when APs can't find the controller, your DNS is not pointing unifi to the IP address of the Unifi controller. | ||
| - | |||
| - | |||
| ping unifi | ping unifi | ||
| - | |||
| - | |||
| from a command line on one of your APs you have ssh'd into and have it successfully resolve to your controller, that's your problem. | from a command line on one of your APs you have ssh'd into and have it successfully resolve to your controller, that's your problem. | ||
| - | + | Also if your controller has more than one NIC configured, you will have a lot less issues adopting any Unifi kit if you ensure the override is enabled. | |
| - | + | ||
| - | Also if your controller has more than one NIC configured, you will have a lot less issues adopting any Unifi kit if you ensure the override is enabled. | + | |