Unifi Shows Adopting Over and Over Again

Adopting an Unifi Access Point in the controller should be really straightforward. But sometimes it just won't piece of work. Y'all keep getting Adoption Failed, or maybe even not able to adopt your access bespeak at all.

The first footstep is to make sure that the inform URL is gear up correctly in the access point. But if that is set correctly then we need to take a different approach to fix the Unifi Adoption Failed issue.

In this article, I will explain different solutions to will assist you to ready the adoption issue.

Why is the Unifi Adoption Failing

Beginning a little bit of background information about why the adoption could be failing. There are a couple of things required to successfully prefer an Unifi Access Point in your controller:

• The access point must not be managed by another controller
• Inform url should be set up correctly – read more about information technology here
• Access Point firmware version should not be to old
• Controller should be up-to-date

The most common event is a firmware mismatch. The access bespeak is for example running the latest firmware version, simply the controller is perchance 10 releases behind. This could cause problems with adopting the access point.

Fix Unifi Adoption Failed

Method 1 – Factory Reset the Access Betoken

To make sure that the access point isn't managed by another (sometime) controller, we are first going to factory reset the access indicate. Make sure that the access point is powered on and printing the reset push button for 10 seconds.

Another fashion to reset the admission point is remotely with SSH.

1. Connect to the access betoken over SSH (using PowerShell for example)
2. Enter the following command to factory reset the AP:

set-default

You tin can reconnect to the access point after the Clearing CFG (configuration) is washed.

With the Access Betoken reset you can at present check if you can adopt the access point in the controller.

Method 2 – Check IP Address of the Access Point

After you lot take factory reset the access point, you should at least run across the access point in the controller. If you don't meet it at all, and so it's possible that the IP range of the access signal doesn't match with the controller.

They both demand to be in the same IP Range to exist able to communicate with each other. You can use the Unifi Discovery Tool to scan your whole network for the admission point. This way you can decide which IP Address the access point has got.

Unifi Discovery Tool

You might need to click the Unifi Family button in the top right corner to switch to the correct view.

If the access betoken is in a unlike IP range, and then double-check your router and Unifi Controller to be sure that simply i them has DHCP enabled. Another skilful option is to connect the access point to the same switch as the controller.

Method 3 – Update the Unifi Controller

Before nosotros update the firmware of the admission point, we are offset going to make certain that Unifi Controller is up-to-appointment.

If you have a Cloudkey or UDM (Pro)

1. Open your Unifi OS
2. Go to Settings > Updates
3. Check the Network application is upward-to-date

If you are running the controller in a Docker container or on Windows so bank check the version that y'all are running in the settings screen:

1. Open the network controller
2. Click on Settings
3. Note the version and check the latest available version here https://www.ui.com/download/unifi/

Subsequently yous accept updated the Unifi Controller, attempt again to adopt the Admission Betoken.

Method 4 – Update the firmware on the Admission Point

If the firmware on the access point is outdated, then you also won't be able to adopt the access point in the Unifi Controller. Commonly you lot update the firmware through the controller, but there is another option.

We tin can manually download the Unifi firmware on the admission signal directly. To do this we are going to connect to the access point over SSH. You will demand to know the IP Accost of the access indicate, if you lot don't run into the IP Address in the controller, then apply Advanced IP Scanner to look information technology upward.

1. Press Windows Key + Ten (or correct-click the startmenu) and choose Windows PowerShell
2. Connect to your access point. Replace the IP Adres below with the address of your access betoken:

# Connect to the access point, with username ubnt ssh [email protected]  # type yeah on the following warning: The authenticity of host '192.168.1.142 (192.168.ane.142)' can't be established. RSA key fingerprint is SHA256:dR0P62KnusGClIgPM1pfsx1QlH6HzrgTLxz0wDk2D4k. Are you certain you lot want to keep connecting (yeah/no/[fingerprint])? yes

3. Enter the password ubnt
4. We now need to observe the correct firmware URL. Open up the Unifi download page and find the firmware for your access point.
5. Click Download and accept the terms.
6. Click Copy URL

7. In the PowerShell Windows, type upgrade and paste the URL that we just copied:

upgrade https://dl.ui.com/unifi/firmware/U7PG2/v.43.56.12784/BZ.qca956x_5.43.56+12784.211209.2338.bin

The admission bespeak will download the firmware and upgrade it. During the upgrade, you won't be able to connect to the admission point. It tin can take a couple of minutes to complete.

You should be able to adopt the Unifi Access point when the upgrade is completed and the status low-cal is solid white.

Wrapping Upward

I hope this commodity helped you lot to gear up the Unifi adoption failed issue. A factory reset is well-nigh of the time needed and brand sure that you lot cheque your firmware versions. If you are running the controller in a docker container, and then make sure that the appropriate ports are forwarded.

In docker, it can assistance to add the --net=host flag to the docker run command.

If yous accept any questions, just drop a comment below.

vanleerfored1985.blogspot.com

Source: https://lazyadmin.nl/home-network/unifi-adoption-failed/