A UniFi Network Controller is most useful when you can reach it from anywhere – from home, on the road, or from a client’s site. Remote access really means two things: you want to open your controller’s management interface from afar, and your devices at remote locations need to talk to it reliably. This guide walks through the official ways to set up UniFi remote access, what each one requires, and when a hosted controller removes the hassle entirely.
What „remote access“ actually means for a UniFi controller
First, an important distinction: the controller manages and configures your UniFi devices, but it does not route your traffic. Access points, switches, and gateways keep working even when the controller is temporarily unreachable. Remote access is therefore about the management connection – not about your live network operation.
That management connection runs in two directions: you reach the interface through a browser or app, and the devices in turn „inform“ the controller about their status. Both need to work over the internet as soon as the controller and the devices are no longer on the same local network.
Option 1: Remote Management via the UniFi Site Manager
Ubiquiti’s standard route is the UniFi Site Manager at unifi.ui.com (or the UniFi app for iOS and Android). You sign in with your UI Account and see every console and site you own or have been granted admin permissions for – all in one place.
Remote Management is enabled by default when you first set up a UniFi console. If you want to check it or turn it on manually, you’ll find the option under Settings → Control Plane → Console in the Advanced section as „Remote Management“.
Direct Connection and performance
When you’re on the same local network as the console, Site Manager automatically activates a direct connection. For a high-performance connection from afar, Ubiquiti requires a UniFi Gateway with a public IP address where TCP port 443 isn’t already taken by a port-forwarding rule. Without these, access still works, but over a less direct path.
Option 2: Self-hosted controller with your own exposure
If you run the controller yourself – for example on a UniFi OS Server or Cloud Key – you can also expose remote access through your own network without Site Manager. That requires a fixed or dynamically resolved public address, clean port forwarding, and a solid security concept. A controller interface left unprotected on the internet is a popular target, so this path belongs in experienced hands.
Option 3: The hosted cloud controller – remote access built in
If your controller runs in a data center from the start, remote access isn’t an extra step – it’s the default. You reach the interface anytime via its fixed address over an encrypted HTTPS connection, whether or not your office has a public IP or sits behind a changing connection. There’s no port forward on your own line and no single point of failure in the form of local hardware.
That’s exactly clevendo’s approach: your UniFi Cloud Controller runs in a German data center (GDPR-compliant), with an individual firewall, DDoS protection, and automatic backups. Your devices at any location inform the controller over the internet (Layer-3 adoption), and you manage everything conveniently through the browser.
Assigning admins and roles properly
Remote access usually means several people should be able to connect – ideally with appropriately scaled permissions. In UniFi you grant access via People → New Admin in Site Manager. Each invited person needs their own UI Account (free at account.ui.com), which you then assign to one or more sites.
The key roles: the Owner is the account that originally set up the console and holds the highest level of access. A Super Admin has full administrative access to a site – including actions like backup restoration and SSH configuration – while some functions remain reserved for the owner. This lets you give service providers or colleagues exactly as much access as they need.
Staying secure with remote access
As soon as an interface is reachable remotely, it becomes a target. A few basics cut the risk considerably:
- Enable two-factor authentication for your UI Account – the login is your first line of defense.
- Assign roles sparingly: not everyone needs Super Admin rights.
- Use an encrypted connection: Site Manager traffic is encrypted in transit – never connect through insecure workarounds.
- Harden self-hosting: if you expose the controller yourself, plan for firewall rules, current updates, and access restrictions.
The access routes compared
| Route | Public IP at your own site required? | Effort | Best for |
|---|---|---|---|
| Site Manager (Remote Management) | Yes for best performance (UniFi Gateway) | Low | On-site UniFi consoles |
| Self-hosting with own exposure | Yes | High | Experienced admins |
| Hosted cloud controller | No | Very low | Location-independent management |
Conclusion
For on-site UniFi consoles, Site Manager is the fastest route to remote access – with a gateway and public IP for maximum performance. If you want location-independent management without maintaining your own exposure, a hosted controller is the calmest option: remote access is built in from the start. If you’d like to move your controller to the cloud or have it professionally managed, the clevendo team is happy to help – just get in touch.
Frequently asked questions
Do I need a public IP address for UniFi remote access?
For a high-performance direct connection through Site Manager, Ubiquiti requires a UniFi Gateway with a public IP where TCP port 443 is free. With a hosted cloud controller you don’t need a public IP at your own site – you reach the interface directly via its address.
How do I enable Remote Management on my console?
Remote Management is active by default after setup. To check or enable it manually, go to Settings → Control Plane → Console and look under Advanced for „Remote Management“.
Can I give several people remote access?
Yes. In Site Manager you invite additional admins under People → New Admin. Each person needs their own UI Account and can be assigned to one or more sites with scaled permissions.
Will my network go down if the controller is unreachable?
No. The controller manages the devices but does not route traffic. Access points, switches, and gateways keep working while the controller is briefly unreachable – only central management pauses.
What’s the difference between Site Manager and a hosted controller?
Site Manager is a central portal through which you reach your on-site consoles remotely. A hosted controller, by contrast, runs entirely in the data center – the management instance itself is already reachable from anywhere, independent of your local hardware.