Unifi controller login url
![unifi controller login url unifi controller login url](https://www.contradodigital.com/wp-content/uploads/2021/03/Ubiquiti-UniFi-Controller-Software-Launch-Browser.png)
To get remote access working in a stable manner, there are a couple more things to do, per my discussion of this at. But if you restrict outbound UDP traffic then remote access will regularly disconnect with a 400 error and have some other problems because of the way the Unifi controller (and some other Unifi devices) use WebRTC for the remote connection. The above config will allow you adopt the cloud controller from a remote session, and to SORT OF launch remote access.
![unifi controller login url unifi controller login url](https://devblogs.microsoft.com/premier-developer/wp-content/uploads/sites/31/2019/06/delete-cancel-1-1-redeploy-refresh-e-your-deplo.png)
However, if you don't have VPN access to the site and need remote access to the cloud key that is stable, there is more to do. This should be enough to get everything working locally, and if you have VPN access to the site, this is all you'll need to do as you can access the controller and devices over the VPN. Unifi controller (cloud key) outbound to wan:ĭNS NTP HTTP HTTPS SMTPS UDP/3478 (STUN) TCP/8543 (UNIFI-CLOUD-ACCESS) TCP/11143 (UNIFI-CLOUD-ACCESS-OLD - probably no longer needed) UDP/5656-5699 (UNIFI-AP-EDU-BROADCAST - maybe optional, or only for AP EDU units) UDP/10001 (UNIFI-AP-DISCOVERY) UDP/1900 (UNIFI-L2-DISCOVERABLE-UPNP) TCP/6789 (UNIFI-MOBILE-SPEED-TEST - optional) PING SSH TCP/8880 (HTTP Portal redirct - optional) TCP/8843 (HTTPS Portal redirect)Īllow the following services both from the cloud key to the other Unifi devices and the other direction:
Unifi controller login url Pc#
To access the cloud key locally you'll need to allow the following services from your management PC to the cloud key:
Unifi controller login url code#
If you're using the FortiGate for DHCP this is a little tricky, as you need to set the Additional DHCP Options to the custom option code of 43, then set the hex value to indicate the sub-type, number of bytes, and IP in hex, like so:Ġ1: suboption 04: length of the payload (4 bytes) c0a80001: 192.168.0.1 in hex Per if you put your Unifi Controller (cloud key in this case) in a different subnet/vlan, you can provide the IP of the controller to other Unifi devices by using DHCP Option 43. I found that if I moved the cloud key to a new subnet, or from a lab with one public IP to a location with a different public IP, that remote web access would stop working till I used ssh to connect and reboot the cloud key. Note that you can use "exec ssh" from remote/cloud access to the FortiGate to access the cloud key. The switches (and newer APs) can now be set to work with tagged vlans, but make sure they're getting untagged native vlans to start with. The cloud key and other Unifi devices all assume native vlans and DHCP to start.
Unifi controller login url free#
Hope this is useful, and feel free to post corrections. Let me know if this isn't appropriate for the forum.Īfter setting up a Unifi Cloud Key, switches, and access points behind a FortiGate, with vlan separation between the cloud key (controller used for management) and other Unifi devices, and with remote access to the Unifi system working through the FortiGate, I thought I'd post what I found that worked to save others some time. Thought I'd post the FortiGate configs to work with some Unifi devices.