Docs › Omada and UniFi controllers
TP-Link Omada & Ubiquiti UniFi
Connecting an Omada or UniFi Controller
Omada (OC200/OC220) and UniFi controllers don't run a provisioning script like MikroTik — they're reached over a private WireGuard tunnel to the billing server instead. You do this once, entirely yourself, from your own controller's local settings — no support ticket needed.
There is no "Controller IP" field when adding one of these devices — connectivity only ever works over this tunnel. A raw local IP is almost never reachable from the billing server (it's usually behind CGNAT), so it isn't offered as an option.
1
Add the device
Go to Routers → Add Router, choose Omada or UniFi as the device type, and fill in the admin username/password and (optionally) the Site ID.
2
Open the Setup Guide tab
On the new router's page, go to the Setup Guide tab. Step 1 there is "Connect this controller/console over WireGuard (required)".
3
Set up the tunnel
Click Set Up WireGuard Tunnel and download the config file it generates. In your controller's own admin UI, go to its VPN client settings (Omada: Settings → VPN Client; UniFi: Settings → VPN → VPN Client) and upload that file.
4
Activate
Once your controller shows the VPN client as Connected, click Activate Tunnel on the Setup Guide page. The billing server verifies a real handshake before switching over — so nothing breaks if the upload was incomplete.
5
Finish the portal setup
Follow the remaining steps on the same page: enable the External/Guest Hotspot Portal on your controller, point it at the billing URL shown, and confirm the Site ID matches.
You can click "Set Up WireGuard Tunnel" again anytime — it's safe even if a tunnel already exists. It reuses the same key and hands you the same config again, in case you need to re-download or upload it to a replacement device.