I recently did two things. 1) Upgrade the firmware on my Ubiquiti Access Point and 2) Replaced my router with PFSense running on an old Xeon-based machine I had. This led to a big problem when trying to get my access point to work, it just wouldn’t connect to the controller. It failed to be adopted by the controller so it couldn’t get its configuration. TLDR: The solution was to remove the device when it was turned off, turn it back on and then adopt the access point from the controller interface
I might have a bit of a unique setup. I only have the Access point and use a Linux server to run the software that manages it instead of the hardware they sell. So that might have caused problems. Overall I’ve been incredibly happy with the alien space-ship looking access point. I’ve never had to reboot it to get it to work and it gets pretty good coverage for being under my couch. Plus I dig the PoE single cable connection for when I eventually get into the attic to mount it to my ceiling. So if you’re looking for something good and relatively cheap, I do recommend it. Its about $80 on Amazon: Click here.
- Unplug and plug back in… No dice.
- Hold reset button with paper-clip for 30 seconds… No dice.
- SSH to the device to set-inform-url… No dice.
This one was interesting though. You can run:
ssh ubnt@<ip of device>with the password ubnt to get to a busybox shell. From there you can run:
set-inform http://ip-of-controller:8080/informand see if it connects.
At this point I considered reflashing the firmware, but didn’t want to go through all the steps of setting up a tftp server, etc. to boot the image correctly. As a last-ditch effort I just unplugged the access-point, logged into the web console and deleted/forgot device, and plugged it back in. And sure enough it worked. So instead of trying even step 3 above, it makes sense just to forget the device and set it up after step 2 above.