UniFi - Change default ports for controller and UAPs

by Ubiquiti Employee ‎03-11-2013 09:46 AM - edited ‎08-13-2013 03:16 AM (18,086 Views)


Readers will learn the default ports used by UniFi controller and how to change them. By default, the UniFi controller will operate on the following ports:

  • unifi.shutdown.port=8081 (used for management purposes)
  • unifi.http.port=8080 (port for UAP to inform controller)
  • unifi.https.port=8443 (port for controller GUI / API, as seen in web browser)
  • portal.http.port=8880 (port for HTTP portal redirect)
  • portal.https.port=8843 (port for HTTPS portal redirect)
  • unifi.db.port=27117 (local-bound port for DB server)


UniFi gives operators the freedom to change these ports from their default assignments. By using a network utility (netstat, etc.), users can determine which ports are in use/opened/closed. The steps are outlined below:

  1. Close any instances of UniFi software running on controller(s)
  2. Modify the file system.properties accordingly—the file can be found in the directory <unifi_base>/data/system.properties
  3. Make sure all ports needed by UniFi are available
  4. Restart UniFi

Example (Windows)

  1. Run “netstat – ano” command in the command line.
  2. Locate the PID for the mentioned port in use.
  3.  Open task manager and select view and select columns , put a check for PID (process identifiers)
  4. Check the process corresponding to the PID located for the port during step 2.
  5. End the process if it is possible.
  6. If not possible go on the location <unifi_base>/data and open the system file with word or notepad.
  7. Modify this file to change the port that was in use.  For example if port 8081 was in use you would modify the line "unifi.shutdown.port=8081" to something like "unifi.shutdown.port=8089" assuming port 8089 was not already in use.

Video tutorial


FCC Compliance Information
For information on compliance with FCC rules and requirements, please read this: FCC Compliance Information
The articles in the knowledge base are voluntarily provided by community members, and Ubiquiti Networks makes no guarantee of the validity of this content.