Connect Ubiquiti APs to a New Controller


  • Service Provider

    I have a Unifi controller that died (not one that I set up or knew about) and the APs need to be migrated to a new controller. I assume that they have to be reset and treated as new, but am hoping that there is a simpler process. Anyone know of any options other than nuke it and start over?



  • @scottalanmiller said in Connect Ubiquiti APs to a New Controller:

    set and treated as new, but am hoping that there is a simpler process. Anyone know of any options other than nuke it and start over?

    If you know the previous Admin password you can try this:
    https://help.ubnt.com/hc/en-us/articles/205146020-UniFi-Advanced-Adoption-of-a-Managed-By-Other-Device

    Otherwise is reset and add again.



  • This is a known controller that was rebuilt by myself just over a year ago.

    It’s filled up the dive previously and with your assistance was fixed

    Not sure on threads- but sure I have at least one thread here on it.

    Difficult to search via the iPhone and 7% battery...



  • If we can’t recover the controller- I have had to cycle them via ssh and their direct ip.



  • Think in the past i've seen AP's appear on a new controller as "Managed by Other" you can then click in the config of the AP and force Adopt to the new controller.

    If you have access to the AP's via SSH issue the set-inform command to the new controller address see if they show up and allow advanced adopt



  • @scottalanmiller said in Connect Ubiquiti APs to a New Controller:

    I have a Unifi controller that died (not one that I set up or knew about) and the APs need to be migrated to a new controller. I assume that they have to be reset and treated as new, but am hoping that there is a simpler process. Anyone know of any options other than nuke it and start over?

    Do you have a backup of the config, if so just setup your new controller and import the configuration.

    They should be adopted without issue.


  • Service Provider

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.



  • @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.


  • Service Provider

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.



  • @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.

    I tried liking it. I just can't do it.


  • Service Provider

    @bbigford said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.

    I tried liking it. I just can't do it.

    And the problem is that it is just a ERL under the hood. But the ERL just can't handle the USG style firmware.



  • @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.

    I know, I wasn't the one that put it in, it is this one: https://www.ubnt.com/unifi-routing/usg/
    They have the newer USG that are bigger. Are those any better?
    https://www.ubnt.com/unifi-routing/unifi-security-gateway-pro-4/
    https://unifi-xg.ubnt.com/usg-xg-8



  • @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.

    I know, I wasn't the one that put it in, it is this one: https://www.ubnt.com/unifi-routing/usg/
    They have the newer USG that are bigger. Are those any better?
    https://www.ubnt.com/unifi-routing/unifi-security-gateway-pro-4/
    https://unifi-xg.ubnt.com/usg-xg-8

    Any better? No. They just give you more throughput and can handle higher density. Same concepts/software. If something requires more than the basic USG, I'm probably going a much different route. Ubiquiti switching/wireless is great, their security though... not so much. Maybe that will change; who knows.


  • Service Provider

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    @penguinwrangler said in Connect Ubiquiti APs to a New Controller:

    @jaredbusch said in Connect Ubiquiti APs to a New Controller:

    Controlled migrations have lots of tools and options.

    But a downed controller has pretty much no option except to default the APs and readopt.

    You will not even be able to SSH into the APs if you cannot log into the controller and get the device admin password for the site.

    @JaredBusch is right. If you lost the controller it is a reset process. I recently went through something similar, however, it was the fact that our ISP at a location I manage decided to change out there cable modem and in doing so changed them from a static IP to a dynamic IP. Which is fine and easier for me but they didn't tell the client that they might have to reconfigure their equipment and didn't even bother to make sure they had internet. Switch cable modem and left. Client calls me and I get there and well the Ubiquiti Secure Gateway wasn't working because it was set to use a static IP on the WAN side. I was mad. So I had to reset the Ubiquiti Secure Gateway. Now here is the kicker, it would show up in my controller once I set the inform address but for some reason at least on the smaller USG's is that you had to ssh into them and set the inform address. Click on adopt in the controller and then while it says adopting in the controller run the inform command in ssh again. If you didn't do that it would be adopted but say disconnected. It was a long night until I found those instructions. Grrrr.

    I hate the USG. Such a piece of crap.

    I know, I wasn't the one that put it in, it is this one: https://www.ubnt.com/unifi-routing/usg/
    They have the newer USG that are bigger. Are those any better?
    https://www.ubnt.com/unifi-routing/unifi-security-gateway-pro-4/
    https://unifi-xg.ubnt.com/usg-xg-8

    It is better hardware under the hood, but it is still UniFi.

    UniFi is shit on a router.