Super helpful! My new device showed up as a client. Used Putty to SSH into the device, and used set-inform with my controller IP. This caused the device to show up under devices and asked to be adopted. PERFECT!
Just adding another thank you to your list of thank yous. For X-mas I'm upgrading my mother's network and I needed to reset the USG after adopting. Your video fixed my "adoption failed" error when my UAG came back online.
@Reilly Chase Many thanks. This is the closest I have come to resolving this problem. But how do I replicate this process on a Windows UniFi controller?
Thank you for this video. It helped solve my problem. I have 4 AP-AC-Pro units. They have been working for a year. I was in the process of making a change to my WiFi network. I used one of the AP's for testing a new setup. I performed a factory reset on the AP and adopted on a new controller. I set up a new network and tested fine. I factory reset again and adopted to original controller (Cloud Key). Adopted fine, WiFi was working in original config. I wanted to make one last test on the new network before changing all 4 AP's to the new network. This time I selected Forget Device in controller (Cloud Key) instead of factory reset then moved the network cable to the new network. The new controller does not see the AP. Then I did a factory reset on the AP. The light starts out white, then goes out, then blinking white, then steady white, then blue. The AP acts like it's still adopted even after factory reset. I believe the database is stuck like you suggested. Instead of editing the database I just installed a Unifi controller on another machine. I imported a "settings only" backup to the other machine and was able to adopt the AP.
Nope- when I type 'info' the Status comes back blank. Unify and APs are latest software and firmware, respectively. I send the set-inform command exactly the way you say and it says to check the controller, but there is nothing on the controller, no message, nothing (says No UniFi devices Have Been Adopted). The controller and APs are on the same network, same IP range, both APs are visible in the Ubiquiti Discovery tool. The controller doesn't show up in the discovery tool, but not sure that it should or shouldn't be? iOS app shows the Unifi controller and the two APs, which it lists as independent but gives no option to adopt from the app. Tells me to do it from the controller, but it shows nothing.
hi, great help from your video, had a problem with a AP not wanting to be adopted to my new setup with the controller in a docker. searching for problems there for hours, but then I just started over and your tip with the set-inform was the problem.... It was a little weird, the input of the inform did not take in the gui, had to do it via ssh in the AP. Jumped over some steps in my troubleshooting.. Thanks for the reset! :-)
i have the server reject problem , i need help with the last bit of the video the audio brock up a little and i was not sure how to pull up that data base ?
Are you effing kidding me!!! I use to love ubiquity but I ran into way too many of these scenarios where you gotta go through all kinds of screwing around To get the device adopted. Ubiquity needs to fix this I have yet to have a clean install of this company's equipment. I have gone away from ubiquity I need equipment that works I'm tired absolutely tired of fighting this company's equipment. In theory this company's equipment is excellent and I wish that it work 100% of the time but to have videos like this where you have to putty in and deal with command line BS just because the thing doesn't work. So aggravating. Every time i have ventured away from Cisco I have been disappointed, And it looks like I'm going back once again.
The most informative resource I was able to find about this problem. Thanks! Where are more technical references that are written to outline these CLI processes?
3:55 - "so the way you can fix this is... " - and then mic connection drops. Could you repeat that part? The artice stops at SSH firmware update. Could you add to it the part for "server reject -endless adoption" problem? How to delete device from the database. The audio in this video drops out at key moments.
Thanks for the feedback. To fix “Server Reject”: On an Ubuntu or Debian UniFi controller: mongo -port 27117 use ace db.device.findOne({‘mac’:’xx:xx:xx:xx:xx:xx’}) If found, do db.device.deleteOne({‘mac’:’xx:xx:xx:xx:xx:xx’}) Then reboot the controller, and reset the device to factory settings with set-default command and try to set-inform it again. For the last one I was talking about the adoption loop that occurs sometimes when the devices shows up as “Adopt and Upgrade” in the controller, you click the button, the device reboots, but then comes up again as “Adopt and upgrade”. Follow this guide to upgrade the firmware via SSH to solve that: support.hostifi.net/en/articles/3561556-how-to-upgrade-unifi-device-firmware-via-ssh
@@ReillyChase Thanks for the answer. So this solution is only for controllers hosted on separate Linux server. I have cloud key gen2. The story is that something went wrong during migrating process to the new controller and my AP has fallen into a adaptation loop (Server Reject status from SSH). New controller could see the AP but just cannot successfully adopt it. "Forget device" did not work coz the device was busy. So I waited for the orange "adopting" status to be changed to red "disconnected" and them the "Forget device" command went through successfully. Thanks for pointing me because it was the same thing like with "db.device.deleteOne", but I managed to do it from UI level.
any chance of some written instructions on what you showed in the video, I cannot keep up with the speed you typed and also the screen text is very small
Thanks for posting. After trying every possible username and password known to man, I was able to find the user name and password for my Unifi devices in the new GUI version console settings page settings/system/advanced/device authentication. Any chance of inserting the actual commands in the "more" section below the video as the focus/resolution of the commands were hard to follow. Thanks for heading me in the right direction.
When I try FORGET it then I see error popup: "There was an error removing UAP-LUBLIN1. Unknown device ." info give me that Server Reject error. I download and unzip the MongoShell mongosh.exe --port 27117 > use ace > db.device.findOne({'mac':'44:d9:e7:a4:a4:00'}) > db.device.deleteOne({'mac':'44:d9:e7:a4:a4:00'}) > db.device.findOne({'mac':'44:d9:e7:a4:a4:00'}) null > exit cmd > net stop UniFi cmd > net start UniFi Official support not help, 4days and they only show me a KB article who are not related for that problem like they have only Leve1 support :( UniFi Controller: 6.0.23.0 This is a solution.
Just want to thank I have been pulling my hair out trying to adopt a radio and turns out it was already installed before. probably defaulted 20 times. You really helped me ty. If I every go to host you will be the one I will use.
Hi, I have a unifi 6 lite ap and it gets a weird ip range when I connect it to my switch (192.168.78.28) instead of my default 192.168.1.xx subnet. It was working fine before now suddenly no matter what I do, I can’t adopt it. I tried resetting it, different cables, different poe switch etc etc. Also double checked the dhcp server and its working. Whenever I plug in an ethernet device it gets the proper ip range (192.168.1.xx). I also can’t ping the device no matter how I connect it to the network. Any ideas?
Hi, i have USG connected to my Fiber router, then a unifi L3 switch towards the USG for LAN...my issue is that both AP's reboots randomly and reconnects and 1 AP consistently has adoption failed, with IP unreachable while the other stays connected....i have to manually reboot it by unplugging the cable. Tried upgrading towards 4.3.24.11355... Manual reset by button and forgot device on the controller and informing by ssh yet these two issues still persists....adoption failed and reboots...Need guidance as i have to reboot daily
Any idea why I cant ping server from SSH CLI. Server can ping device. Uninstalled controller software, that helped with new setup. Can't get controller software to see device. Thanks. Device can see router
Can you add how to get access via Putty? I get an error "Permission Denied." I researched and toggled the advanced settings within my controller and still cannot log into my AP LR. I cannot even find my USG. I thought forgetting the device and pressing the hard reset button would help, hours later I am much worse off. I wish I never upgraded my controller's software. That is when my trouble started as no devices were connected after that but my internet still worked. I can't print now, so I am forced to deal with this network issue. This UniFi has been a major pain to deal with. It is not user friendly.
If you're in commandline to login via SSH, you can provide the username before the IP address you're SShing into separated by @. For instance: ssh root@192.168.1.1 This should log you in to the gateway and allow you to type in the password to login.
I get a "null" reply when I do the db.device.findOne command. I tried the mac address of the device to be deployed and a device that is already deployed, I get the "null" response regardless. Someone has an idea?
Hi - even though the video is almost a year old - i also learned a lot - thanks for that :-) --- unfortunately for me it did not do the trick - mongo db entry dont exist - ssh into the device not possible... unifi finds the device (viewport) but says unable to adopt... if you read this message.... i would really like to pick your brain :-)
I'm running into that issue right now and haven't been trying to resolve it for a couple of days. I've contacted help support with no response. So, still waiting. Were you able to resolve yours?
@@hostifi there was some Internal Failed in logs and that's all + rp=5 , as 'rp' seems to be some kind code error. I can't give you more details because I switched to localhost controller for now and bought Raspberry Pie and I will put Unify Controller on Kubernetes and migrate AP and Switch from localhost controller to that on Kubernetes
Is there a community forum? I have this error when I ssh into the USG Status: Unable to resolve (unifi:8080/inform) ubnt@ubnt:~$ set-inform unifi:8080/inform Adoption request sent to 'unifi:8080/inform'. Use the controller to complete the adopt process. I've reset the device already
What the heck did you say just before "It's pretty easy to pick up" ~50 second mark? Not to sound like an English teacher but your enunciation is such that I cannot understand half of what you are saying!
Hi and thanks for all your info, great tutorial, how would I do this on a Windows base, On an Ubuntu or Debian UniFi controller: mongo -port 27117 use ace db.device.findOne({‘mac’:’xx:xx:xx:xx:xx:xx’}) If found, do db.device.deleteOne({‘mac’:’xx:xx:xx:xx:xx:xx’}) Then reboot the controller, and reset the device to factory settings with set-default command and try to set-inform it again
Super helpful! My new device showed up as a client. Used Putty to SSH into the device, and used set-inform with my controller IP. This caused the device to show up under devices and asked to be adopted. PERFECT!
Just adding another thank you to your list of thank yous. For X-mas I'm upgrading my mother's network and I needed to reset the USG after adopting. Your video fixed my "adoption failed" error when my UAG came back online.
Very helpful, could not have got past "Adoption Failed" without it
Thanks for watching, glad it helped you out!
this really helped.. solved my problem very easily rather than doing a full reset and then adopting the devices again
Thank you for posting this concise video on how to resolve Adoption problems.
What is the software you use for command prompt and Debian because it’s not present in mine
what a clear and to the point and no fluf.... bravo
@Reilly Chase Many thanks. This is the closest I have come to resolving this problem. But how do I replicate this process on a Windows UniFi controller?
Thank you for this video. It helped solve my problem. I have 4 AP-AC-Pro units. They have been working for a year. I was in the process of making a change to my WiFi network. I used one of the AP's for testing a new setup. I performed a factory reset on the AP and adopted on a new controller. I set up a new network and tested fine. I factory reset again and adopted to original controller (Cloud Key). Adopted fine, WiFi was working in original config. I wanted to make one last test on the new network before changing all 4 AP's to the new network. This time I selected Forget Device in controller (Cloud Key) instead of factory reset then moved the network cable to the new network. The new controller does not see the AP. Then I did a factory reset on the AP. The light starts out white, then goes out, then blinking white, then steady white, then blue. The AP acts like it's still adopted even after factory reset. I believe the database is stuck like you suggested. Instead of editing the database I just installed a Unifi controller on another machine. I imported a "settings only" backup to the other machine and was able to adopt the AP.
Nope- when I type 'info' the Status comes back blank. Unify and APs are latest software and firmware, respectively. I send the set-inform command exactly the way you say and it says to check the controller, but there is nothing on the controller, no message, nothing (says No UniFi devices Have Been Adopted). The controller and APs are on the same network, same IP range, both APs are visible in the Ubiquiti Discovery tool. The controller doesn't show up in the discovery tool, but not sure that it should or shouldn't be?
iOS app shows the Unifi controller and the two APs, which it lists as independent but gives no option to adopt from the app. Tells me to do it from the controller, but it shows nothing.
hi, great help from your video, had a problem with a AP not wanting to be adopted to my new setup with the controller in a docker. searching for problems there for hours, but then I just started over and your tip with the set-inform was the problem.... It was a little weird, the input of the inform did not take in the gui, had to do it via ssh in the AP. Jumped over some steps in my troubleshooting.. Thanks for the reset! :-)
i have the server reject problem , i need help with the last bit of the video the audio brock up a little and i was not sure how to pull up that data base ?
Good job Bud - Your support is definitely better that Unifi keep up the good work,
Are you effing kidding me!!! I use to love ubiquity but I ran into way too many of these scenarios where you gotta go through all kinds of screwing around To get the device adopted. Ubiquity needs to fix this I have yet to have a clean install of this company's equipment. I have gone away from ubiquity I need equipment that works I'm tired absolutely tired of fighting this company's equipment. In theory this company's equipment is excellent and I wish that it work 100% of the time but to have videos like this where you have to putty in and deal with command line BS just because the thing doesn't work. So aggravating. Every time i have ventured away from Cisco I have been disappointed, And it looks like I'm going back once again.
The most informative resource I was able to find about this problem. Thanks! Where are more technical references that are written to outline these CLI processes?
Literally just saved my Job
3:55 - "so the way you can fix this is... "
- and then mic connection drops. Could you repeat that part?
The artice stops at SSH firmware update. Could you add to it the part for "server reject -endless adoption" problem? How to delete device from the database. The audio in this video drops out at key moments.
Thanks for the feedback. To fix “Server Reject”:
On an Ubuntu or Debian UniFi controller:
mongo -port 27117
use ace
db.device.findOne({‘mac’:’xx:xx:xx:xx:xx:xx’})
If found, do
db.device.deleteOne({‘mac’:’xx:xx:xx:xx:xx:xx’})
Then reboot the controller, and reset the device to factory settings with set-default command and try to set-inform it again.
For the last one I was talking about the adoption loop that occurs sometimes when the devices shows up as “Adopt and Upgrade” in the controller, you click the button, the device reboots, but then comes up again as “Adopt and upgrade”. Follow this guide to upgrade the firmware via SSH to solve that: support.hostifi.net/en/articles/3561556-how-to-upgrade-unifi-device-firmware-via-ssh
@@ReillyChase Thanks for the answer. So this solution is only for controllers hosted on separate Linux server. I have cloud key gen2. The story is that something went wrong during migrating process to the new controller and my AP has fallen into a adaptation loop (Server Reject status from SSH). New controller could see the AP but just cannot successfully adopt it. "Forget device" did not work coz the device was busy. So I waited for the orange "adopting" status to be changed to red "disconnected" and them the "Forget device" command went through successfully.
Thanks for pointing me because it was the same thing like with "db.device.deleteOne", but I managed to do it from UI level.
Thanks! The mongodb deletion fixed it!
Wow man you really know your stuff, you have now saved me hours off work, sorted out my AP, thanks again
any chance of some written instructions on what you showed in the video, I cannot keep up with the speed you typed and also the screen text is very small
Great video! Did not help with the adoption of a USW-Enterprise-8-PoE, though.
May I ask if this is same procedure to perform, I have here Unifi 16 port switch even after Reset the switch still I cant Adopt or failed.
Great video tips, thanks for sharing!!!
Thanks for watching!
Old video but thanks you just saved my ass!
Thanks for posting. After trying every possible username and password known to man, I was able to find the user name and password for my Unifi devices in the new GUI version console settings page settings/system/advanced/device authentication.
Any chance of inserting the actual commands in the "more" section below the video as the focus/resolution of the commands were hard to follow.
Thanks for heading me in the right direction.
Thanks for watching!
When I try FORGET it then I see error popup: "There was an error removing UAP-LUBLIN1. Unknown device ."
info give me that Server Reject error.
I download and unzip the MongoShell
mongosh.exe --port 27117
> use ace
> db.device.findOne({'mac':'44:d9:e7:a4:a4:00'})
> db.device.deleteOne({'mac':'44:d9:e7:a4:a4:00'})
> db.device.findOne({'mac':'44:d9:e7:a4:a4:00'})
null
> exit
cmd > net stop UniFi
cmd > net start UniFi
Official support not help, 4days and they only show me a KB article who are not related for that problem like they have only Leve1 support :(
UniFi Controller: 6.0.23.0
This is a solution.
How do you determine what the IP address is to start? I have done an IP search on the network and the switch does not show up.
I'm trying to adopt USW-Lite-8-PoE but it stays "Adopting" for hours, and never adopted... Anyone know what wrong is it? Thanks!
Hi there, thanks for watching. If you can ask our team at support@hostifi.com they'll be sure to help!
@@hostifi thanks for your response! Yes, I did contact them; they just sent me the document link. I tried it a few times. I gave up….
Just want to thank I have been pulling my hair out trying to adopt a radio and turns out it was already installed before. probably defaulted 20 times. You really helped me ty. If I every go to host you will be the one I will use.
was nice, but i can't install the mongoDB on the windows linux commad terminal
Awesome video man! Saved me a whole headache I was ready to factory reset all of the devices but this worked!
Hi, I have a unifi 6 lite ap and it gets a weird ip range when I connect it to my switch (192.168.78.28) instead of my default 192.168.1.xx subnet. It was working fine before now suddenly no matter what I do, I can’t adopt it. I tried resetting it, different cables, different poe switch etc etc. Also double checked the dhcp server and its working. Whenever I plug in an ethernet device it gets the proper ip range (192.168.1.xx). I also can’t ping the device no matter how I connect it to the network. Any ideas?
Hello Ali! Thanks for watching the video. Do you have a modem before your router or another DHCP server on the network?
i’m getting a switch that is constantly adopting. deleting/error in and out.
Hi, i have USG connected to my Fiber router, then a unifi L3 switch towards the USG for LAN...my issue is that both AP's reboots randomly and reconnects and 1 AP consistently has adoption failed, with IP unreachable while the other stays connected....i have to manually reboot it by unplugging the cable. Tried upgrading towards 4.3.24.11355... Manual reset by button and forgot device on the controller and informing by ssh yet these two issues still persists....adoption failed and reboots...Need guidance as i have to reboot daily
exactly what I needed to know. Thanks!
Thanks for watching! Glad it helped
what aplication to run mongoDB?
hello i have a uap-ac mesh i try to upgrade but putty say /tmp/fwupdate.bin!
Invalid firmware. Exit status for firmware check = 65024.
I need to do it but Under Windows to remove the Forgeted device that is stuck in the Unifi Controler.
Any idea why I cant ping server from SSH CLI. Server can ping device. Uninstalled controller software, that helped with new setup. Can't get controller software to see device. Thanks. Device can see router
How can I adopt a USG in 192. ip, where I’m using a USG/key in 10. ip?
I suspect you need to get your connecting client's IP stack on the same net?
I'm about to try that myself.
Can you add how to get access via Putty? I get an error "Permission Denied." I researched and toggled the advanced settings within my controller and still cannot log into my AP LR. I cannot even find my USG. I thought forgetting the device and pressing the hard reset button would help, hours later I am much worse off. I wish I never upgraded my controller's software. That is when my trouble started as no devices were connected after that but my internet still worked. I can't print now, so I am forced to deal with this network issue. This UniFi has been a major pain to deal with. It is not user friendly.
If you're in commandline to login via SSH, you can provide the username before the IP address you're SShing into separated by @.
For instance:
ssh root@192.168.1.1
This should log you in to the gateway and allow you to type in the password to login.
I get a "null" reply when I do the db.device.findOne command. I tried the mac address of the device to be deployed and a device that is already deployed, I get the "null" response regardless. Someone has an idea?
GOD BLESS YOU. I'M SUBSCRIBING TO YOUR CHANNEL, Thank you so much 👏
Cant access putty. It says "access denied" eventhough i put the right username and password. Help me man
Hey Marshal, take a look at this guide we made here: support.hostifi.com/en/articles/6337741-unifi-how-to-factory-reset-an-access-point
How can I get to controller CLI if I have windows installed controller? or how can I edit "ACE" database under windows?
Take a look here: help.ui.com/hc/en-us/articles/360006634094-UniFi-Network-Controller-Repairing-Database-Issues-on-the-UniFi-Controller#5
@@hostifi how to change, for example "inform_url" of the device, which you previously found with 'db.device.findOne' ?
Thank you so much
You're most welcome
Thank you!
You're welcome!
Thank you for sharing. This has saved my day.
Thank you for this. Saved me lots of time and I learnt something new
Many thanks, this helped me a lot!
You're welcome!
Hi - even though the video is almost a year old - i also learned a lot - thanks for that :-) --- unfortunately for me it did not do the trick - mongo db entry dont exist - ssh into the device not possible... unifi finds the device (viewport) but says unable to adopt... if you read this message.... i would really like to pick your brain :-)
Does not work. Not able to connect after resett. Get the Message: connection closed by remote host
Very helpful video, thanks for sharing!
APs lose connection anytime internet or power goes down. Any suggestions?
Thank great information and the steps was easy and quick, I was up and running in 2 Minutes.
I don't have a server what can I use for the host name?
The controller ip address i guess
I want to kiss you, you are my hero. I've tried everything, and you're the only method that worked. Thx!!!
You are welcome!
has anyone had this problem where you do a factory reset on the USG and the default ID and password don't work?
I'm running into that issue right now and haven't been trying to resolve it for a couple of days. I've contacted help support with no response. So, still waiting. Were you able to resolve yours?
@@dand7451 No i have not been able to figure it out yet.
thanks for the video, it solved my problem more then once!
Thanks!
Unfortunately that doesn't work. Removed but still Server Reject.
Can you post the output of "info" command here for us to check it out?
@@hostifi there was some Internal Failed in logs and that's all + rp=5 , as 'rp' seems to be some kind code error. I can't give you more details because I switched to localhost controller for now and bought Raspberry Pie and I will put Unify Controller on Kubernetes and migrate AP and Switch from localhost controller to that on Kubernetes
Thank. now i can solve my problem.
My default gateway not available
Thank you!! So helpfull
This was great, Well done. :)
bless
Is there a community forum? I have this error when I ssh into the USG
Status: Unable to resolve (unifi:8080/inform)
ubnt@ubnt:~$ set-inform unifi:8080/inform
Adoption request sent to 'unifi:8080/inform'. Use the controller to complete the adopt process.
I've reset the device already
Hey! Feel free to reach out to our support team support@hostifi.com
What the heck did you say just before "It's pretty easy to pick up" ~50 second mark? Not to sound like an English teacher but your enunciation is such that I cannot understand half of what you are saying!
Hi and thanks for all your info, great tutorial, how would I do this on a Windows base,
On an Ubuntu or Debian UniFi controller:
mongo -port 27117
use ace
db.device.findOne({‘mac’:’xx:xx:xx:xx:xx:xx’})
If found, do
db.device.deleteOne({‘mac’:’xx:xx:xx:xx:xx:xx’})
Then reboot the controller, and reset the device to factory settings with set-default command and try to set-inform it again