I know this is a beaten question but everytime I start reading all the previous posts on this subject I become more confused :-) so here's what I got.

I’m looking at migrating our Unifi Controller 5.5.20 to another server. I found this great “How To” https://help.ubnt.com/hc/en-us/articles/115002869188input_string=migration+now+connected+%28migrated%29

but have some questions before I do this.

1. I have three sites on three different subnets in physically different buildings/locations. I take it I will follow the instructions for all three sites, exporting, importing, and forgetting, then on to the next site. Will being on different subnets be a problem?
2. On the new controller, should I restore the actual controller backup before I start importing sites? I want as little data brought over from the old controller, just configuration settings.
3. I do have a DNS entry for “unfi” which points to the old controllers IP address. Should I change this to point to the new controllers IP address before I start the migration or after. I’m assuming I want to do this before because in step 8 it asks to put in the URL for the new controller and if I have the DNS already changed I can put in http://unifi for the URL leaving the :8080 and /inform fields alone. Unfortunately it looks like the “set-inform” was configured to the IP address of the old controller and not the “unfi” DNS entry.

Note that I cannot keep the same IP address for the controller. The server that hosts the old controller has other services running on it. 

Thanks for your input

I hope to deploy dozens of In-Wall AC units and am looking for an internal DHCP controller so guests are on a separate network.  Many of the AirMax products such as Nanostation and others offered this capability.  But I can't find it using UnitFi controller V5.5.20.  Did UBNT remove this nice feature in UniFi? I wish In-Wall AC had a SOHO router mode.  If no DHCP for In-Wall AC, I'll have to use another vendor.

Hi everyone!

I'm facing  a  strange symptom almost every day with one of my  4 APs (AP AC PRO):

I have the controller software running on a  cloud key.  Everything works fine but if I oen the controller software I  see 1 LAN device (my switch) and for WLAN devices (my 4 APs) in the upper right corner. However in the lower left corner it says  4 devices (1 LAN, 3 WLAN).

clicking on devices, I get the information that all 5 devices are connected, but the order is a bit different from usual. This morning "WLAN-KG" was on top of the list.  I clicked on  this device and  got an empty window on the right. Now chance to configure anything. It works for  the other 4 devices. Checking with my iPhone, the  AP WLAN-KG gives  me full wifi connection. In the topology chart this AP is marked with a "?".  Checking with  the iOS app, I was able to configure this AP normally.  After restart  of the AP (that works  using  the controller software) everything was fine again. Yesterday I had the same problem with another AP.

Is there  a software bug (cloud keay, controller, AP)?

Clemens

Current setup consists of an ASUS RT-AC66U in the basement near the cable modem. Up until recently it has worked decently, mainly because my computer was in the living room above the area where the router was, maybe 20-30 feet distant with one floor in the way. I could get 140-150 MBPS there.

Unfortunately, I relocated my desk to the play room. 50-60 feet from the router with th same floor in the way. Now 5G connectivity is useless. I connect, but get 3-5 MBPS on 5G. On 2.4G, I can get 30-40MBPS. This isn't terrible, but doesn't exceed the speed of my ISP. So a solution is needed.

I initially looked into the UniFi AP lineup. Unforunately, these only seem to work when mounted the ceiling. This would work, but I have a wall panel with Cat6 wiring just waiting to be used, so that got me looking at the in-wall units. My primary concern there is rang. They're designed to cover one room well, but I'm hoping they can do slightly more. Can anyone tell me what the coverage pattern is from one of these? IE, do they cover back from the mounting hole, backward behind the unit? Or do the primarily broadcast into the room of the wall that they're mounted on.

Any help in choosing a solution would be helpful.

Just got the Unifi UAP-AC-HD and am having trouble with the controller starting.

I downloaded the latest Unifi controller software (5.5.20).

I am running this on a mac...OS Sierra (10.12.6)

As per a lot of posts here the controller will not startup.  The UI shows this:

Initializing UniFi Controller ...
Starting UniFi Controller ...
Server taking too long to start...
Start-up failed.

The server.log shows this:

[2017-09-16 15:22:57,175] <launcher-ui> INFO  launcher - Initializing UniFi Controller ...

[2017-09-16 15:22:57,365] <launcher-monitor> INFO  launcher - Starting UniFi Controller ...

[2017-09-16 15:22:58,399] <launcher> INFO  system - ======================================================================

[2017-09-16 15:22:58,400] <launcher> INFO  system - UniFi 5.5.20 (build atag_5.5.20_9565 - release) is started

[2017-09-16 15:22:58,400] <launcher> INFO  system - ======================================================================

[2017-09-16 15:22:58,403] <launcher> INFO  system - BASE dir:/Applications/UniFi.app/Contents/Resources

[2017-09-16 15:22:58,408] <launcher> INFO  system - Current System IP: 192.168.0.20

[2017-09-16 15:22:58,571] <launcher> INFO  system - Hostname: Shanes-MacBook-Pro.local

[2017-09-16 15:22:58,734] <launcher> INFO  db     - waiting for db connection...

[2017-09-16 15:22:59,237] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

[2017-09-16 15:23:00,320] <launcher> INFO  db     - *** Factory Default *** Database exists. Drop it

[2017-09-16 15:23:00,331] <launcher> INFO  db     - waiting for db connection...

[2017-09-16 15:23:02,474] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

[2017-09-16 15:23:02,490] <launcher> INFO  stat   - *** Factory Default *** Stat Database exists. Drop it

[2017-09-16 15:23:03,594] <launcher> WARN  discover - unable to join multicast group 233.89.188.1 on awdl0 (/fe80:0:0:0:bc69:85ff:fe33:6786%awdl0)

[2017-09-16 15:23:03,717] <launcher> INFO  webrtc - WebRTC library version: EvoStream Media Server (www.evostream.com) build v1.0.20 - Gladiator - (built for MacOSX-10.9-x86_64 on 2017-06-15T19:07:21.000) OpenSSL version: 1.0.2k usrsctp version: d350f4ec3e9bc0ed compiled on machine: Darwin jenkins-slave-2.local 13.4.0 Darwin Kernel Version 13.4.0: Mon Jan 11 18:17:34 PST 2016; root:xnu-2422.115.15~1/RELEASE_X86_64 x86_64

[2017-09-16 15:29:58,207] <launcher-monitor> ERROR launcher - Server taking too long to start...

[2017-09-16 15:29:58,212] <launcher-ui> ERROR launcher - Start-up failed.

The mongod.log is quite long however does not appear to have any obvious errors.

As per other posts I have tried downgrading to java 6.  This did not make any difference.

At a bit of a loss here so any help appreciated.

Hi, just installed the AP but can't download the software onto my iPad?

Hi There

I just want to make sure that I fully understand this before I go and action it.

I am admining 3 remote site - all have different IPs and on each site - there are 2 APs

Site 1 - 2 APs + CloudKey

Site 2 - 2 APs - Dynamic IP

Site 3 - 2 APs - Dynamic IP

Each site has a different purpose and are all set up different 

I am wishing to admin the APs via the single CK. The CK at Site 1 works well and is allowing me to control the APs at Site 1.

If I am wishing to admin Site 2 and Site 3 APs via the Same CK....

Am I correct in thinking, I would just need to go back to Site 2 and Site 3 and do the "set-inform" function via SSH and point the APs to the CK IP Address??

Once they have been "set-inform" then I would simply log into the CK and adopt them from there?

Does it matter if the remote sites have a Dynamic IP?

I am in the process of setting the CK to a static IP (dyndns etc)

I just want to make sure that I am on the correct path before heading out to do this - as the sites are located some distance from each other.

Thanks for your guidance