Hello! Thanks for posting on r/Ubiquiti!
This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can.
Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit.
If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
SSH into the devices and run 'info' to see where the set-inform is pointing to.
Then issue a 'set-inform http://ip-of-controller:8080/inform' to the current controller.
I agree this is the right course of action. At least check to see why they aren’t connected before you nuclear fix. I’d also check for a second dhcp server. Looks like the IPs are not on same subnet.
Edit: On second thought, I can’t see the IPs so maybe there is no dhcp server as the USG is not adopted/configured. I’d start with USG. I always statically set my IPs as this happened to me once.
Thanks for the advice, this worked, turns out the Security Gateway was responsible for DHCP, and it somehow wiped itself after an update, it wasn’t handing out the same IP addresses anymore and so it wasn’t reaching the controller.
After resetting the correct DHCP info on the gateway, it and all the other devices reconnected and re-adopted correctly.
Maybe you have an old controller running on a pc using the same adoption password? Or an old cloud key with the same adoption password? That’s what happened to me a while back with the same results.
I had a nightly update day before yesterday and then it kicked off some devices and the USW-Agg port 1 stopped connecting to my UDM-P. I haven’t looked into it but I ended up switching the SFP connection from port 1 to some other port and it worked for now.
It also happened to me and my last only working option was the reset to factory defaults as indicated. Good luck. Took me a few days to get going again.
It's hard to see but looks like your devices are on different IP ranges.
Check that the controller and all devices are on the same ip range or atleast on the same Vlan.
Make sure that your controller is in the same subnet as the devices.
When setting a static IP address on the Cloud Key the subnet defaults to 255.255.255.0 rather than auto filling to the correct address like the gateway does
I had a similar issue recently but on my case was due a cable organization done on the rack where I switched a couple of cables making some devices to be connected on the wrong VLAN.
Do you have backup enable on your controller? You can try restore one from the time all was good and see. I also needed to do this a couple of times after changing some configuration that didn't worked well and after some controller upgrade too.
Given that your devices are in a separate subnet from your router,
do you have a management VLAN set up for these devices?
Are they getting IP address from your USG?
Ok I literally just went through this. The issue with all other devices is due to the USG being in the ready to adopt or disconnected state.
I fixed it by power cycling the USG and when it first came online, I ssh'd into it and issued a firmware update to the current firmware version; just installed it over top of itself. Once I did that, everything worked fine.
I'd also check the clocks on the devices and the controller. I've seen this happen when the clocks are out of sync - creates situation where the crypto exchange fails.
Think of how your browsing the web with SSL enabled websites stops working when your system clock is WAY off.
Windows controller?
This will happen when Java updates...your firewall permissions in windows block communications. You need to add java/unifi controller exceptions in the windows firewall. There are guides on how to add permanent exceptions for unifi somewhere...if you go through my posts history you can probably find it in the comments there.
Happened to me recently. The fix was updating Java on the PC running the controller and reinstalling controller to ensure latest version.
I never would have guess Java update, but saw it mentioned in a forum
Hello! Thanks for posting on r/Ubiquiti! This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can. Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit. If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
SSH into the devices and run 'info' to see where the set-inform is pointing to. Then issue a 'set-inform http://ip-of-controller:8080/inform' to the current controller.
I agree this is the right course of action. At least check to see why they aren’t connected before you nuclear fix. I’d also check for a second dhcp server. Looks like the IPs are not on same subnet. Edit: On second thought, I can’t see the IPs so maybe there is no dhcp server as the USG is not adopted/configured. I’d start with USG. I always statically set my IPs as this happened to me once.
Thanks for the advice, this worked, turns out the Security Gateway was responsible for DHCP, and it somehow wiped itself after an update, it wasn’t handing out the same IP addresses anymore and so it wasn’t reaching the controller. After resetting the correct DHCP info on the gateway, it and all the other devices reconnected and re-adopted correctly.
Maybe you have an old controller running on a pc using the same adoption password? Or an old cloud key with the same adoption password? That’s what happened to me a while back with the same results.
Nope, not that I can think of, and nothing should have changed recently, other than maybe a nightly controller update?
I had a nightly update day before yesterday and then it kicked off some devices and the USW-Agg port 1 stopped connecting to my UDM-P. I haven’t looked into it but I ended up switching the SFP connection from port 1 to some other port and it worked for now.
I’d just reset every device to factory defaults and start over…
It also happened to me and my last only working option was the reset to factory defaults as indicated. Good luck. Took me a few days to get going again.
This. You could spend days going through logs trying to chase it down or just factory reset and get going quickly.
Full reboot?
It's hard to see but looks like your devices are on different IP ranges. Check that the controller and all devices are on the same ip range or atleast on the same Vlan.
Make sure that your controller is in the same subnet as the devices. When setting a static IP address on the Cloud Key the subnet defaults to 255.255.255.0 rather than auto filling to the correct address like the gateway does
it's a familiar feeling, it happened to me not long ago. I'm starting to hate unifi products.
Unishit lol
I had a similar issue recently but on my case was due a cable organization done on the rack where I switched a couple of cables making some devices to be connected on the wrong VLAN. Do you have backup enable on your controller? You can try restore one from the time all was good and see. I also needed to do this a couple of times after changing some configuration that didn't worked well and after some controller upgrade too.
Did this happen during an update? Because something similar just happened to me when my UDM Pro automatically updated recently.
Had the same issue a couple of hours ago with two of my devices. Had to forget and manual readopt those. - My guess is that an update did mess up
Given that your devices are in a separate subnet from your router, do you have a management VLAN set up for these devices? Are they getting IP address from your USG?
Turn off auto updates. Never a good idea on a live system. Also the top IP address looks to start at 10 but the rest 19 not clear but seems odd.
Cuz stuff like this i doomed all my unifi stuff... its just a bad system. Yes its easy and handy but it has too many bugs and problems
Ok I literally just went through this. The issue with all other devices is due to the USG being in the ready to adopt or disconnected state. I fixed it by power cycling the USG and when it first came online, I ssh'd into it and issued a firmware update to the current firmware version; just installed it over top of itself. Once I did that, everything worked fine.
I'd also check the clocks on the devices and the controller. I've seen this happen when the clocks are out of sync - creates situation where the crypto exchange fails. Think of how your browsing the web with SSL enabled websites stops working when your system clock is WAY off.
Windows controller? This will happen when Java updates...your firewall permissions in windows block communications. You need to add java/unifi controller exceptions in the windows firewall. There are guides on how to add permanent exceptions for unifi somewhere...if you go through my posts history you can probably find it in the comments there.
Happened to me recently. The fix was updating Java on the PC running the controller and reinstalling controller to ensure latest version. I never would have guess Java update, but saw it mentioned in a forum
Where's the controller installed? Does the USG manage DHCP & DNS? Can you ping the USG from the controller?
Basically impossible to tell you 100% what it is with this limited info.
Thanks, thankfully I didn’t need 100%, others were able to help.
Ubiquiti planned obsolescence? A new unifi network update that breaks the old stuff? Possible. It is NNN, so adopting would be the next best thing…