UniFi controller ports: defaults and how to change them (2026)
The default UniFi controller ports depend on what runs your controller. On the legacy UniFi Network Server, the web interface is on port 8443 and devices inform on port 8080. On a UniFi OS console, the web interface is on port 443. UniFi OS Server keeps 8080 for devices and dropped 8443 in version 5.1.15.
You can change the ports only on the legacy Network Server. Ubiquiti doesn't support changing them on consoles or UniFi OS Server.
| Web interface | Device inform | Change ports? | |
|---|---|---|---|
| UniFi Network Server (legacy) | TCP 8443 | TCP 8080 | Yes, in system.properties |
| UniFi OS console (Cloud Gateway, Cloud Key) | TCP 443 | TCP 8080 | No |
| UniFi OS Server | TCP 11443 in practice (see below) | TCP 8080 | No |
Checked against Ubiquiti's documentation on September 25, 2026.
UniFi Network Server default ports
The UniFi Network Server is the standalone Network application for Windows, macOS and Linux, often still called the "UniFi controller". Ubiquiti now labels it legacy and recommends UniFi OS Server for new self-hosted setups.
These are the main ones, from Ubiquiti's Required Ports Reference. The full list also covers gateways, Site Magic and other UniFi applications.
| Port | Used for |
|---|---|
| TCP 8080 | Device and application communication (inform) |
| TCP 8443 | Web interface and API |
| UDP 3478 | STUN, for device adoption and communication |
| UDP 10001 | Device discovery during adoption |
| UDP 1900 | Discovery on the local network ("Make application discoverable on L2 network") |
| TCP 8880 to 8882 | Guest portal redirection over HTTP |
| TCP 8843 | Guest portal redirection over HTTPS |
| TCP 6789 | UniFi mobile speed test |
| UDP 5514 | Remote syslog capture |
| UDP 10101 | Client fingerprinting |
| TCP 28082 | Device packet capture and support-file downloads |
| TCP 27117 | Local database (MongoDB) |
| TCP 8081 | Shutdown port, used by the application itself |
Ubiquiti's install guide opens four of these on the host firewall: TCP 8080, TCP 8843, UDP 10001 and UDP 3478. After installing, you open the web interface at https://localhost:8443.
UniFi OS console ports
On a UniFi OS console, such as a Cloud Gateway or a Cloud Key, you reach the web interface on port 443. Ubiquiti's local management guide puts it simply: "Self-hosted Network Servers use port 8443, while other devices use port 443."
Devices still inform on TCP 8080 and use UDP 3478 for STUN, which helps devices behind a router find their public address. For Remote Management through Site Manager, a console needs outbound TCP 443 and TCP 8883.
UniFi OS Server ports
UniFi OS Server is Ubiquiti's current self-hosting software. It uses a different set of ports than the Network Server.
The release notes for UniFi OS Server 4.3.6 (September 2025) list its ports: 3478, 5005, 5514, 6789, 8080, 8444, 8880, 8881, 8882, 9543, 10003, 11084 and 11443.
Three changes since then matter:
- Version 5.1.15 (May 2026) removed the unused external port 8443.
- On Linux, the same release restricted port 11084 to loopback, so it only answers on the server itself.
- Device support-file downloads now need port 28082 to be reachable from the devices.
Guest portals moved too. Ubiquiti's self-hosting article says captive portals are served on port 8444, changed from 8843 on the Network Server.
Ubiquiti doesn't say which port serves the web interface. In our own installs it's 11443, so you open https://<server-ip>:11443. Our Windows installation guide shows the same address.
Which ports need to be reachable
Ubiquiti's self-hosting article gives TCP 8080 and UDP 3478 as the examples of ports to open. Those two carry device traffic, so devices at other sites must be able to reach them.
A few rules we follow for any self-hosted controller:
- Only open the web interface port to the addresses your admins use.
- Keep TCP 27117 closed to the network. It's the local database.
- Open the guest portal ports only if the controller serves a guest portal.
- UDP 10001 and UDP 1900 are for discovery on the local network, so there's no reason to open them to the internet.
If you need to reach a controller behind a router, our guide to UniFi port forwarding covers the router side.
How to change ports on the UniFi Network Server
Ubiquiti says changing default ports "is only supported on self-hosted UniFi Network Servers (Windows/macOS/Linux)". You do it in a file called system.properties.
1. Back up and stop the application
Ubiquiti says to make a backup first. Our guide shows how to back up a UniFi controller.
Then close the UniFi Network application. On Linux, stop the service:
sudo service unifi stop
2. Open system.properties
The file is in the data folder of the UniFi installation. Based on the folders Ubiquiti's help articles use, that is:
| System | File location |
|---|---|
| Windows | C:\Users\<username>\Ubiquiti UniFi\data\system.properties |
| macOS | ~/Library/Application Support/UniFi/data/system.properties |
| Linux (Debian, Ubuntu) | /usr/lib/unifi/data/system.properties |
The file is created the first time UniFi Network runs successfully. If it isn't there, start the application once and close it again.
3. Set the new port
Add a line at the bottom of the file with the port you want to change. Ubiquiti's current example changes the shutdown port:
unifi.shutdown.port=8089
A 2020 version of Ubiquiti's system.properties article listed the keys for the other ports, with their defaults:
unifi.http.port=8080
unifi.https.port=8443
portal.http.port=8880
portal.https.port=8843
unifi.db.port=27117
unifi.stun.port=3478
Based on those keys, moving the web interface to 9443 would take unifi.https.port=9443. Ubiquiti's current article no longer lists them, so test the change before you rely on it.
Keep the line clean. Ubiquiti warns that a change is ignored if the line has extra spaces, comments or characters such as #. Lines that start with # are comments.
4. Restart and check
Start the UniFi Network application again. On Linux:
sudo service unifi start
Ubiquiti's article also says to trigger provisioning manually on each site after changing the file. Then open the web interface on the new port and allow that port in the host firewall.
If you change the inform port
Devices that are already adopted keep calling the old inform address. If you move port 8080, expect them to lose contact until you point each one at the new port with set-inform. Plan that before you make the change.
"Port 8443 is used by other programs"
This startup error means another program on the machine already uses the port. Find it and stop it, or move UniFi to another port with unifi.https.port. The same applies to 8080 and unifi.http.port.
On a fresh install this gets tricky. The file only exists after a successful start. If the clash stops the very first start, free the port first.
Can you change ports on UniFi OS Server or a console?
No. Ubiquiti says changing default ports is supported only on self-hosted UniFi Network Servers. It doesn't document a way to change the ports on UniFi OS Server or on a console.
On UniFi OS Server, that means the host has to fit around UniFi. If another program on the server already uses 8080, 8444 or 11443, move that program.
Frequently asked questions
What is the default port for the UniFi controller?
On the legacy UniFi Network Server, the web interface uses TCP 8443 and devices inform on TCP 8080. On a UniFi OS console the web interface is on port 443.
Which port do UniFi devices use to reach the controller?
TCP 8080, for inform. They also use UDP 3478 for STUN. Both need to be reachable from every site the controller manages.
Does UniFi OS Server still use port 8443?
No. UniFi OS Server 5.1.15 removed the unused external port 8443. The captive portal uses 8444 instead of 8843.
Can I change the port on UniFi OS Server?
No. Ubiquiti documents port changes only for the legacy Network Server. For UniFi OS Server, keep the default ports free on the host.
Final thoughts
Changing a controller port is a small edit on the legacy Network Server. On UniFi OS Server and consoles, Ubiquiti doesn't support it. Port trouble on a self-hosted controller often comes from the host instead: another program on 8080 or 8443, or a firewall that blocks inform.
For a home lab, running your own controller and keeping those ports in order is fine. For client networks, UniHosted runs managed UniFi OS Server hosting, with daily backups, tested updates and IP access control on paid plans.
Related guides
Keep reading
UniFi OS Server: what it is, requirements and how to get it (2026)
UniFi OS Server is Ubiquiti's free software for self-hosting UniFi. What it replaces, what it can run, system requirements, and how to install and update it.
Read guideUniFi Site Manager: what it is and how to use it (2026)
UniFi Site Manager is Ubiquiti's free portal at unifi.ui.com for managing all your UniFi sites in one place. What it does, how to open it and where it stops.
Read guideHow to Install UniFi OS Server on Windows (2026)
Install UniFi OS Server on Windows 11 with WSL2: full walkthrough, system requirements, and the service-mode limitation you must know before deploying.
Read guide