Self Hosted UniFi Controllers

Cloud vs. Local Hosting

A self-hosted UniFi controller can be deployed in two primary ways: cloud-hosted or locally hosted. In a cloud-hosted setup, the controller is managed on a third-party platform like AWS, providing remote access and flexibility. On the other hand, a locally hosted controller resides on a physical server within your own infrastructure, offering more control but requiring direct network access. Both options allow you to manage your UniFi network independently, with differences in accessibility and server management.

Public IP Requirement for Self-Hosted Controllers

To ensure proper connectivity, a static public IP is required for self-hosted UniFi controllers. If your controller is cloud-hosted, you will need the public IP address of the cloud instance where it is running. For locally hosted controllers, the public IP of the host location is necessary. This IP address must be static to maintain consistent remote access to the controller and avoid interruptions caused by IP changes. Without a static public IP, the connection to your controller may fail when the IP address changes.

Port Forwarding Requirement for Self-Hosted Controllers

For self-hosted UniFi controllers, port forwarding is essential to enable external access. If your controller is cloud-hosted, the port forward rule must be configured in the hosting console, such as AWS or similar cloud platforms, to allow traffic through port 8443. On the other hand, for locally hosted controllers, the port forward rule must be applied on the primary firewall or router of the physical location hosting the controller. In both scenarios, port 8443 must be opened to ensure seamless communication between MyPlace and your UniFi controller.

To enhance security, MyPlace can provide a list of service IPs, allowing you to restrict access to the port and ensure it is only accessible to authorized systems.