Security update: We discovered CVE-2026-54405 (CVSS 7.5). Ubiquiti has patched it—update UniFi Network to 10.4.57 or later.

Read the advisory

How to access a UniFi controller locally or remotely

On the local network, you open your UniFi controller in a browser at its IP address. The port depends on what runs it: 443 on a UniFi OS console and 8443 on the legacy UniFi Network Server. On UniFi OS Server, our installs answer on 11443. From anywhere else, you use Site Manager at unifi.ui.com, or a VPN into the site.

This guide covers both, per setup. Last checked against Ubiquiti's documentation on September 25, 2026.

Which address to use

Your controller runs on Local address Remote access
UniFi OS console (Cloud Gateway, Cloud Key, NVR) https://<console-IP>, or unifi/ if you have a UniFi Gateway Site Manager, Direct Remote Connection or a VPN
UniFi OS Server https://<server-IP>:11443 Site Manager, or the server's own address
Legacy UniFi Network Server https://localhost:8443 on the same machine, https://<server-IP>:8443 from another one A VPN into the network. Ubiquiti's update docs suggest Site Manager also covers Network Server 8.6 and later

Ubiquiti calls the device or server that runs UniFi Network the "control plane". Most people still call it the controller, so this guide does too.

How to access the UniFi controller locally

Local access works without an internet connection. You need to be on the same local network as the controller, or connected to it through a VPN.

Ubiquiti's UniFi Local Management article gives the steps:

  1. Open a browser and enter the IP address of your controller.
  2. If you have a UniFi Gateway on your network, you can type unifi/ instead.
  3. Sign in.

You can also use the UniFi mobile app. It lists the UniFi instances it detects on the local network.

Which port to use

The same article says self-hosted Network Servers use port 8443 and other devices use port 443. Port 443 is the default for https://, so on a Cloud Gateway or Cloud Key you don't need to add a port.

UniFi OS Server works differently. Ubiquiti lists port 11443 among the ports it uses, but doesn't say which port serves the web interface. In our own installs it's 11443. Version 5.1.15 removed the unused external port 8443. Our UniFi OS Server guide covers the rest of the setup.

The legacy UniFi Network Server still uses https://localhost:8443. Ubiquiti now labels that software as legacy and calls UniFi OS Server the new standard for self-hosting.

Which login to use

If Remote Management is on, you sign in locally with the same UI account you use at unifi.ui.com. For local-only deployments, Ubiquiti's local management article gives admin as the default username. Its password recovery article says local-only credentials are created during setup, so try the ones you chose then. If the sign-in itself fails, our UniFi login guide covers the common problems.

If you can't find the IP address

Connect your phone to the same network, open the WiFiman app and tap Discovery. This is the method Ubiquiti gives for finding the controller's IP address.

The browser's certificate warning

Your browser may warn that the connection isn't private. Ubiquiti says you can safely ignore this. On UniFi OS Server you can upload your own TLS certificate under Settings > Control Plane > Console > Certificates.

How to access the UniFi controller remotely

Ubiquiti's term for this is Remote Management. It runs through UniFi Site Manager at unifi.ui.com and the UniFi mobile app. Older guides call it Cloud Access.

  1. Go to unifi.ui.com, or open the UniFi mobile app.
  2. Sign in with your UI account.
  3. Click the site you want to manage.

Remote Management is on by default when you set up a UniFi console. On UniFi OS Server, you turn it on by signing in with a UI account after installing. If a site is missing, connect locally, go to Settings > Control Plane > Console, and enable Remote Management (Enabling UniFi Remote Management).

You don't need to open any inbound ports for this. The controller needs outbound TCP 443 and 8883, and Ubiquiti says that includes self-hosted instances. Its troubleshooting list also names DNS on UDP 53 and time sync on UDP 123.

Direct Remote Connection

On the same local network, Site Manager connects to the console directly, which is faster. From outside, it falls back to cloud-assisted access.

Direct Remote Connection gives you that direct link from outside too. Enable it under Control Plane > Console. It needs a UniFi Gateway with a public IP, and TCP port 443 can't be used by a port forwarding rule (UniFi Remote Management via Site Manager).

Controllers in a data center

A UniFi OS Server on a cloud server has no local network for you to join. You open it at its own address in a browser, or through Site Manager if Remote Management is on. The devices it manages can sit at many different sites.

Remote access to the network: Teleport and VPN

Ubiquiti now uses "remote access" for something else: reaching the local network itself through a VPN or port forwarding (UniFi Remote Access: VPN and Port Forwarding). Once you're connected, the local address from the table above works as if you were on site.

Teleport

Teleport is Ubiquiti's zero-configuration VPN, built on WireGuard (UniFi Gateway - Teleport VPN).

  • It needs a Next-Gen gateway or a UniFi Cloud Gateway running UniFi OS.
  • You turn it on under Network Settings > VPN and send an invitation.
  • The recipient connects with the WiFiman app on a phone or computer.
  • An invitation expires after 24 hours and works on one device at a time.
  • It works when both the gateway and the client are behind NAT, sharing a public IP address with other devices. In some cases the gateway's WAN needs IPv6.

Our post on accessing a UniFi controller without port forwarding compares Teleport with other tunnel options.

WireGuard, OpenVPN and L2TP

A UniFi gateway can also run a WireGuard, OpenVPN or L2TP server. These need a public IP address. Ubiquiti says a static IP keeps the connection stable over time.

Port forwarding

You can forward the controller's port to the internet, but Ubiquiti points out the risks. The exposed device carries the security responsibility, and the traffic isn't encrypted by default. For a management interface, Site Manager or a VPN is the safer choice.

Remote Management vs remote access

Remote Management Remote access (VPN)
What you reach The controller, through Site Manager The whole local network
Where it runs Ubiquiti's cloud, or directly with Direct Remote Connection The UniFi gateway at the site
Inbound ports to open None None for Teleport. Most other VPNs need a public IP
Works for Cloud Gateways, Cloud Keys, UniFi OS Server and Official UniFi Hosting Any controller on that network

Frequently asked questions

Can I access my UniFi controller without internet?

Yes. Ubiquiti says sites remain fully manageable through direct local access when the internet or cloud connection is down. Use the local IP address.

Do I need to open ports for UniFi remote access?

No, as long as you use Remote Management through Site Manager. It only needs outbound TCP 443 and 8883. Teleport also works without a public IP.

Why doesn't my controller load on port 8443?

Ubiquiti gives port 8443 for the legacy UniFi Network Server and 443 for other devices. In our installs, UniFi OS Server answers on 11443. Version 5.1.15 removed its unused external port 8443.

Can I use Teleport with any UniFi gateway?

No. Ubiquiti lists two options: a Next-Gen gateway, or a UniFi Cloud Gateway running UniFi OS.

Final thoughts

For your own network, a UniFi console with Remote Management covers both local and remote access. Add Teleport if you need the rest of the network from outside.

Client networks are different. Every controller has to stay online, updated and backed up for you to reach it. If you'd rather hand that off, UniHosted runs UniFi OS Server for MSPs with daily backups and tested updates on paid plans. Your hosted controllers show up in Site Manager next to your other sites.