Only thing I see different is that the current LTS is 5.6.42 and my backups are from 5.6.40. I had the same results of seeing devices but not clients. I then remove the existing docker and deleted the appdata/unifi folder and created a new docker and restored from the backup file. The next step I took was to download a backup file from Unifi Controller. Everything was working perfect before but the issue now is I can see my devices in the Unifi Controller but I can't see any clients. I restored my appdata using CA Appdata Backup / Restore v2 and installed Unifi-Controller LTS. I had to replace my cache drive and recreate my docker.img. It is a beta feature that doesn't want to work well with dockers at the moment, and Ubiquiti doesn't support dockers. And remember, DO NOT TURN ON AUTO OPTIMIZE. For those devices that do not connect, do set-inform after sshing in. All your settings will go back to normal, and then all your devices will connect. Go through the wizard like it is a fresh install AND TURN OFF auto optimize when you get to the admin/authenticate screen, then finish the wizard normally.įinally you can then go back to settings and maintenance and do the backup file. DO NOT use the backup file from the wizard when you first launch into your docker. After you do this you will have to uninstall and blow away the docker in its entirety. Settings -> Maintenance -_> Download Backup. The solution fortunately is not a big deal, but dang did it take some time to figure out!įirst of all make sure you do a new backup file. What ever you do, for now do not turn on auto-optimize, if you do you'll lose your UAP connection as soon as you power cycle. This can be done though a usual SSH session or opening a debug terminal from your controller (click on the device, then the tools button, then debug terminal) depending on the state of your device.įor those having issues with UAP devices showing disconnected and set-inform not working I found the problem. I think that many may be running into this problem depending on their docker network setup.įor those having adoption problems, if you want to check your devices to see where they're getting stuck with adoption loops, you can SSH into the device and run "info" which will show the current set-inform IP address. ![]() I wonder if adding the set-inform address in the controller should be part of the instructions to save frustration. Glad it worked for you looking through this thread, I see lots of adoption issues. No need to change the docker to host with this change. One I changed the above settings in the controller everything connected properly. I tried to do the initial installs of the AP and got the adoption loop when I had the docker to set to bridge. Prior to setup/adoption, devices have a set of default credentials.This worked perfectly for me. Ssh The UXG will use = ‘root’, but the will be the shared password set in your UniFi Network Application. For example, a Dream Machine Pro (which is a UniFi Cloud Gateway) with an IP address of 192.168.1.1 can be accessed as follows: Ssh for UniFi Consoles (UDM Pro / UNVR / Cloud Key) and UniFi Gateways (UXG Pro) is always ‘root’. The format of the command used to establish an SSH connection is as follows: Linux and macOS devices can use their native terminal. The device you are using has a command line interface (CLI) capable of establishing a Secure Shell (SSH) connection. ![]() View and configure them by navigating to UniFi Network > Settings > Advanced > Device Authentication.ģ. The credentials consist of a random string of characters. UniFi Network Devices: SSH is enabled by default.To enable it, navigate to UniFi OS > Console Settings > SSH. UniFi Consoles: SSH is disabled by default.UniFi Network devices and UniFi Consoles (Dream Machines, Cloud Keys, etc.) have independent SSH settings. This may consist of using a laptop connected to the same WiFi network, or hardwired directly to the device.Ģ. ![]() You are connected to the same local network as the device/console you plan to connect with via SSH. Inexperienced users risk making changes that may degrade network performance, or even worse, completely break your deployment. Proceed with caution. We do not recommend using SSH unless instructed by one of our Support Engineers as part of advanced troubleshooting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |