When I go to the controller there is no where (other then the normal adopting proces via Chrome) where I can adopt the AP. After that the set-inform command will be given after each startup.Īnd the prompt is given again.Go back to ssh to give the set-inform command for a second time.I can give the set-inform command and after that I see a list with three items I can ssh and check the info of the device. After 30 seconds I get a message that I need to check if the AP is in default factory settings and if the controller is reachable. I can see the AP as a device when I click it to adopt I see it is trying to adopt the AP. If the AP was previously managed, then you’re going to need to get the username and password from the old controller which is under System Settings > Controller Configuration > Device SSH Authentication. After minutes the status changes to pending again. Grab the IP that was obtained via DHCP and then SSH into the Unifi access point using the default ubnt / ubnt username and password combo. As soon as I click the button to set inform the status of the AP in the Mac App changes to Adopting. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. ![]() They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. and I can reach the dashboard over http 8080-port so to me it seems open). These cookies may be set through our site by our advertising partners. I can set the inform URL in the manage tab (I tried the ip:8080/inform, I tried I tried my ddns, etc. I can click the Adopt button, after a few seconds I see a message that the AP is adopted, but 2-3 seconds later the AP shows up again as a device waiting for adoption. This was added in the same environment (but a lesser version of the controller of course).Īll have the same result I can ping/ssh the AP and the AP gets discovered. I have on AC-pro connected to the controller, it has been connected for almost a year now. The device is upgraded to the latest firmware 3., the controller is on the latest docker build. I have followed all manual around, from using the IOS-app, to the Chrome-extention to SSH, but nothin seems to work. It will not show up on my device list, and stays in the client list. After a few seconds I get a message that the device is adopted, but 2 seconds later it is discovered again. I can sent the inform command and I can click the Adopt button in the controller. Antes de fazer isso verifique se o UAP consegue. The AP gets discovered and I can ssh to it. Outra opo bastante tradicional acessar o dispositivo UniFi via SSH e setar manualmente o set-inform atravs da linha de comando (CLI). I expect the AP to be added to my devices when I press (of command over ssh) Adopt. I want to add another AP (UAP-AC an old square one) to my existing setup. Note: A screenshot of your configuration page if using a gui is acceptable What do you expect to happen? I used the settings as told in dockerhub. Sorry, do not know where to get the logs. Latest What complete docker command or docker-compose.yml do you use to launch the container (omitting sensitive values)? ![]() If there were port conflicts it shouldn't be possible to start the container anyway.DSM 6 - docker container What tag are you using The host is running other containers but there are no conflicting ports. The docker container is running on a Raspberry Pi connected to wired network. My inform URL is :8080/inform I have devices in the controller on the local network with the controller and devices that are external. The inform URL is the IP Address of your controller followed by the port number: 8080/inform. The other is a direct copy of linuxserver.io example: version: "2.1" I recently moved my controller over to a docker container. Type ssh ubnt192.168.1.142 (replace 192.168.1.142 with the IP Address of your access point) Enter the default password ubnt (or lookup the SSH details in your controller) Set-Inform URL. ![]() The first configuration is based on jacobalberty/unifi: version: "3.7" It's possible to manage already connected devices and to find new devices but adopting them results in a never ending "adopting" status. I have followed several guides and opened all ports listed here. 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".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |