Ubiquiti device discovery tool cannot find cloud key

Ubiquiti device discovery tool cannot find cloud key install#
Ubiquiti device discovery tool cannot find cloud key windows#

Don't exclude all port forwarded ports from policy routing.Fix a bug which may cause to be provisioned to devices for both the management and STUN URLs.

Ubiquiti device discovery tool cannot find cloud key windows#

Fix a potential bug affecting autobackup on Windows 10.Fix displaying IP address of gateway discovered by Discovery Tool.Hide Fast Roaming feature for WEP networks.Allow choosing the department in the chat window.This will be fixed in a future release.Д¬ontroller bugfixes/changes since 5.8.28: Port mapping for USG (UGW3) is incorrect under performance statistics.If you start an airTime scan while airView is running, then airView will stop and you'll need to perform a stop/start sequence to get it working again.A stop/start sequence should restore functionality. It is expected that airView will stop occasionally.If you start both a 2.4GHz and 5GHz scan in quick succession, then it will fail.

If you enable it, and it still isn't working, then you may need to force a refresh without cache. airTime will not work if a radio is disabled and/or there isn't any SSID present.There may be some version specific exceptions to this list. The controller's server.log will contain a log message skip provisioning duplicate fixed IP for user indicating which was omitted where there are conflicts. For configurations that already contain duplicates, only the most recently active device will have its fixed IP provisioned to USG. The same IP cannot be assigned to more than one device. Fixed IPs (DHCP reservations) are now required to use unique IPs.This allows you to define the preferred uplinks for a downlink/wireless AP. We added the ability to set uplink priorties.Again, this option should be enabled on downlink/wireless UAPs only.release then this may be enabled on wired APs. If upgrading from 5.6>5.7 then this already be disabled on wired APs, but if upgrading from an earlier 5.7.If you disable this option on a downlink/wireless AP, then your AP will be disconnected from the network and require further action (including physical access).This option should be disabled on wired APs, but is required to be enabled on wireless APs.The controller will not start if it is set to bind to a privileged port (Config>Wireless Uplink.As always, err on the side of caution, and make a backup before upgrading. Please be patient, this process could easily take 15+ minutes, depending on the amount of historical stats, as well as the system specs. It is expected to see mongo using most, if not all, of the available CPU cycles during this process. The initial database migration will take longer than normal.This is most likely to be an issue on Ubuntu 18.04 LTS, as it currently offers MongoDB 3.6.x. Linux systems must be running a version of MongoDB prior to 3.6.x.There is a linked guide with instructions. If you previously used Google Maps for a site map, then you have to enable this feature again by adding an API key.

If you need them you need to go to Settings>Site and check Enable advanced features. Features like airtime fairness, bandsteering, load balancing and minimum RSSI are default disabled.Official UniFi MIBs can be downloaded from HERE and HERE (those are 2 different files).Please use non-DFS channels if you need to use wireless uplink on dual band UAPs.

DFS channels can not be used for wireless uplink in the US.

There are some rough guidelines in the article linked above. It's worth noting that maximum throughput will be affected when using QoS, as traffic is not offloaded.

Smart Queue QoS is similar to the implementation as in EdgeOS (see HERE).

So, if I have a SSID set to use VLAN 10, I cannot use VLAN ID 10 for RADIUS controlled VLAN users as those users will not get an IP.

You cannot re-use a VLAN ID for dynamic VLAN if it is set as a static value for another SSID on the same AP.

Ubiquiti device discovery tool cannot find cloud key install#

Please see HERE and download the missing version (64bit offline Windows install package).

Windows users must have ењ†4 Java installed as we only support 64-bit WebRTC library.

As always, make a backup prior to upgrading.