Unifi Download Network Controller
Eliana Pomerantz
You cannot install UniFi controller on your router. Use something simple like RPi for that if you really need your controller running 24x7 or install it on your desktop if you need it only for occasional configuration changes and maintenance tasks.
Unifi Controller is a controller to all unifi devices which is connected by API so each devices doesn't have to run web server (which is lighter). Usually it's installed in desktop for fire and forget management, but there are some cases where unifi controller installed in mini server or stand alone device for cloud based management and other function like hotspot control.
Extra effort must be made to make adoption work when running in Docker. The default network type for Docker (bridge) means containers are not accessible on the network. For Layer 2 adoption, the documentation for Jacob Alberty's image mentions using host networking or the macvlan network. I've used host networking with this Docker image in Linux and it works well, however at the time of this writing (2022-04-10) host networking is not available in macOS Docker Desktop. I haven't tried using macvlan but it might work well (with either image, even though the LinuxServer.io documentation doesn't mention it). For Layer 3 adoption, it looks like you must enter the Docker host's IP in the UniFi Network Application's settings (the documentation for both Docker images has details of where to find the setting).
You can also run the Network Application "headlessly." I haven't tried it, but the instructions at -the-unifi-controller-headless-on-mac/ look promising. Note that you'll need to use a different exec string than the ones suggested on that page.
Do you have any host overrides set for the hostname of the controller? Basically there is a setting where after the devices connect to the controller if you have this set it will change the inform URL.
I have the same problem, when trying to start the UniFi interface
Java-based controller in web browser I get: Cannot access this website.
But I do the same procedure on another computer without Kaspersky protection and it starts normally.
I should have mentioned I did try that IP, which is the IP of my windows machine running the controller. So, I think it must either be the wrong login credentials (UN / PW) or the wrong Port. But I suspect the default 443 Port is probably not the problem. So, most likely bad credentials. Ubiquiti / UniFi has separate login credentials for the controller app and the online account - tried both of those. Also tried the Home Assistant login credentials. Any other thoughts?
Allow control of network access to clients configured in the integrationIntegrations connect and integrate Home Assistant with your devices, services, and more.
[Learn more] options by adding MAC addresses. Items in this list will have a Home Assistant switch created, using the UniFi Device name, allowing for blocking and unblocking.
Get entities reporting receiving and transmitting bandwidth per network client. These sensors are disabled by default. To enable the bandwidth sensors, on the UniFi integration page, select Configure, go to page 3/3 and enable the bandwidth sensors.
This will show if there are firmware updates available for the UniFi network devices connected to the controller. If the configured user has admin privileges, the firmware upgrades can also be installed directly from Home Assistant.
If you don't have a config then you'd have to rebuild. The key is if you have the SSH key of all your devices. If you can SSH into it then it seems like you do. If you have these keys then you should be able to setup half the network in advance and adopt your devices afterwards with minimal downtime. Most importantly you won't have to climb any ladders or deface any paper clips.
"The backups I have are unfortunately considered 'invalid' by the console."
What backups do you have? They should be files with a .unf extension. If you have any of those backups, I recommend setting up a new controller on any spare computer you have and then importing the backup during the new conrtroller setup. Maybe on eof them will work for you. Then you could make a new backup with the working temop controller, and use that to set up a new controller.
I don't know what the "hard drive" is on a Gen 2 CK, but can you pull the hard drive from the CK and connect it to another computer to search for .unf backups?
Gregg
Good point. My backups all have the version number. I have used them on newer controllers than the backup version, but it's probably a good idea with the OP's issue to install a temp controller of the same version of any .unf files that may be found. Then make a backup of that controller, upgrade it to whatever version the production controller is running, then backup and import to the production controller.
All of that is assuming that a .unf back can be retrieved from the CK or from a management computer that may have had a backup saved.
Gregg
The reason I brought this up is that last fall, I was testing restores of one of my controllers on a spare PC. In doing so I was also testing restores of older backups 5.11.50 to 6.2.26 and for some reason this failed. I didn't keep note of the error. I then installed the older version and stepped up until I was at the latest build.
I'm trying to host the Unifi Controller in a docker container but I can't adopt a new device (access point) unless I set networking mode to "host". I have followed several guides and opened all ports listed here. It's possible to manage already connected devices and to find new devices but adopting them results in a never ending "adopting" status.
The docker container is running on a Raspberry Pi connected to wired network. The host is running other containers but there are no conflicting ports. If there were port conflicts it shouldn't be possible to start the container anyway.
To add to the above solution, once I updated the controller IP in the settings it was necessary to restart the docker container in order for it save the changes for good. Also a good idea to SSH in your AP and run a quick info command (just type info after login) to verify that the Status shows connected and to the right IP and not the internal docker network:
I think you need to get your requirements straight. Do you need standard "401" browser authentication or does your application have a standard form login page? We don't know your software, we can't help without the details. Use a working version of your application and check with the browser developer tools the ongoing network traffic during login.
NOTE: These ports need to be open at the gateway/firewall as well as on the controller host. This would be achieved by creating port forwards on the gateway/firewall where the controller host is located.
Comprehensive network customization has always been a touchstone of the UniFi Network application, and a guiding principle for our developers who work tirelessly to refine it. However, providing such an immense degree of user control can sometimes complicate our larger pursuit to simplify IT for every type of user. We want our settings to provide a wealth of options while also being easy to navigate and understand. Otherwise, network optimization is only possible for the most technically adept.
UniFi is a community of wireless access points, switches, routers, controller devices, VoIP phones, and access control products. It can be used for the corporate network and also for the home network. An Unifi network controller manages all the equipment in the UNIFI network. The best part of the Unifi network is that its controller can be hosted online with a Ubiquiti account using an Unifi Cloud Key, giving online access to the network to manage the Unifi devices and the connected client so can handle most of the operations remotely.
Having an UniFi Controller on the cloud allows us easy deployment of hardware. On any UniFi network where we have UniFi Security Gateway (USG) Installed, any UniFi equipment plugged into the network is immediately recognized by the Unifi Controller and is also ready for adoption. Whenever the controller adopts the device, the device receives the correct configuration and comes up in the network within a short period.
760c119bf3