Unifi network controller 5.11.50 release

Important notes in unifi network controller 5.11.50 release:

UNIFI network controller 5.11.50 release stage: Stable

  • Update the OUI table.
  • Fix authentication failure tracking.
  • Fix invalid switch satisfaction scores.


(Recommended) – Create an up-to-date backup before upgrading your controller in the event any issues are encountered.

  • Existing UniFi Network controllers must be on one of the following versions in order to upgrade directly to this version:
5.11.49 and earlier 5.11.x versions.
5.10.27 and earlier 5.10.x versions.
5.9.33 and earlier 5.9.x versions.
5.8.30 and earlier 5.8.x versions.
5.7.28 and earlier 5.7.x versions.
5.6.42 and earlier 5.6.x versions.
Most earlier versions are also supported for direct upgrade, going back to 3.1.0.


  • An updated/current version of Java 8 must be installed on the system hosting the controller software. Java 9 and later are not yet supported.
  • As of UniFi Network controller 5.9, if using Cloud Access, the host system/device requires outbound 8883/tcp to be open/unrestricted. Find up-to-date port requirements here.
  • Minimum supported device firmware for UAP/USW is 4.0.9, and for USG it’s 4.4.34.
  • SSH Authentication settings are now hidden behind the Advanced Features option.
  • If you have any ‘service DNS forwarding options’ configuration defined in config.gateway.json, it will overwrite the provisioning of statically defined name servers, leaving you with no DNS. Either remove the ‘service dns forwarding options’ portion of config.gateway.json, or add additional ‘options’ lines defining name servers, such as ‘server=’, ‘server=’, etc.
  • PoE passthrough control was implemented for UAP-IW-HD which means that the default for PoE passthrough is now disabled instead of enabled. If you were using this feature before then you will need to re-enable it via the device property panel.

Microsoft Windows specific:

  • Users running 64-bit Windows should only have 64-bit Java installed. If you have 32-bit Java installed then we recommend uninstalling it.

macOS Specific:

  • We stopped bundling Java as of UniFi Network 5.11.47. If you’re installing that release or later please make sure you have manually installed a current release of Java 8 beforehand. Only the Java Runtime Environment (JRE) is required.
  • Oracle JRE 8 offers the simplest path as it will simply “just work” without requiring any changes. We may investigate alternative JVMs and update this message accordingly.

Debian/Ubuntu specific:

  • For Debian/Ubuntu users installing via our repo, please update your APT source (see HERE).
  • Currently, we only support MongoDB 3.4. We’re working on updating support before end of life this fall. We have instructions for Ubuntu users in our HC article HERE (see section 2.2).


4ca994fc80b98b323eb250d19dbed8b1 *UniFi-installer.exe
0265d7001502bb8ab711c67a6ee00ab9 *UniFi.pkg
8ff5468348a64dc308ba96836aff3bbc *UniFi.unix.zip
c212d48a18bca0d78ad89d6d385752c6 *unifi_sysvinit_all.deb
601df32736f41e40a80a3e472450a3e1 *unifi_sh_api
SHA256(UniFi-installer.exe)= a6f8517da4e83fa20dc30e39ec588b96daeac241e30e0deb42985988900a76d6
SHA256(UniFi.pkg)= 4a231813694c2ae05c1d8f9c44b6a1887835176fb75d9d16c56695c8bf8eb63a
SHA256(UniFi.unix.zip)= 18846f808c6758f540f222d725a65935734d59b055c8e406955585dd0df4d817
SHA256(unifi_sysvinit_all.deb)= 7656654aaaa69b064e05db115303d20fb06b03a7efbb962a6b7eb2bb343acf6d
SHA256(unifi_sh_api)= 1791685039ea795970bcc7a61eec854058e3e6fc13c52770e31e20f3beb622eb


For more announcements and details about the unifi controller check the here.

I hope the information was helpful. If you liked the article and if it was helpful please support and donate.

Please contribute to the production of this content by leaving your ‘tip’ in the comments below.

Leave a Comment