Skip to main content

Unifi Cloud | Troubleshooting Unrecognized Discovered Systems

Overview ✨

The UniFi Cloud (Site Manager) Inspector may discover child systems with generic or unfamiliar aliases, including UniFi Network - super, UniFi Network - Default, or a domain-based name. These names typically reflect the source controller’s type or configured site name rather than a Liongard-specific failure.
​

⚠️ Accuracy note: The exact alias depends on the controller metadata returned by Ubiquiti. Treat the displayed name as a clue, not definitive proof of a specific hardware model or internal database structure.

Common Causes

Displayed alias

Likely explanation

Recommended validation

UniFi Network - Default

The UniFi site or application still uses its default name.

Open the corresponding controller and review its site or application name.

UniFi Network - super

The connected controller is returning a generic legacy or application-level identifier.

Use the host URL, controller identifier, and Ubiquiti Network Servers view to identify the source.

UniFi Network - hostname/domian.ui.com

The controller is represented by a hostname or remote-access endpoint instead of a friendly site name.

Match the hostname and controller identifier against the customer’s self-hosted or remotely managed deployment.

Identify the Source Controller

Use the steps below to identify which UniFi controller (and which site) a discovered system belongs to. This is especially helpful when the discovered alias is generic (e.g., UniFi Network - super).

Method 1 - From the Parent Inspector DataPrint (Table View)

  1. In Liongard, open the Parent UniFi Cloud Inspector.

  2. Open the latest DataPrint and switch to Table View.

  3. Go to Discovered.

  4. Filter by the Alias that is confusing (e.g., UniFi Network - super).

  5. Expand the row and locate Config.

  6. Copy the Site Host URL value (it will look similar to): https://api.ui.com/v1/connector/consoles/<HOST_ID>

This URL is useful as an identifier inside the DataPrint, but partners typically cannot use it directly to view the system in the UI (see “Open in UniFi UI” below).

Method 2 - From the Discovered Systems Screen (Edit / Pencil Icon)

  1. Navigate to Admin → Discovered Systems in Liongard.

  2. Find the discovered UniFi entry.

  3. Click the Edit (pencil icon) in the Actions column (before the inspector name).

  4. In the discovered system configuration, capture the following fields (when present):

    • Controller URL

    • Host ID

    • Site ID

These values are the fastest way to map the discovered entry to the correct UniFi environment.

Open the controller directly in the UniFi portal (Host ID URL translation)

If you have a Host ID that appears under the connector URL format:

https://api.ui.com/v1/connector/consoles/<HOST_ID>

You can often open the legacy controller directly by switching the base URL to:

https://unifi.ui.com/network-servers/<HOST_ID>

Example

📝 Do not rely on the alias alone. Confirm ownership using at least two identifiers, such as the host URL and controller identifier, before changing access or archiving an inspector.

Resolution Procedures

Choose the scenario that matches what you find after identifying the Host ID/controller.
​

Scenario A - Old / Offboarded client controller still visible (orphaned access)

This is common when a previous MSP relationship ended but the UniFi cloud access was never removed.

Recommended actions

  1. Confirm it’s truly not an active client

    • Use the Host ID to open it via unifi.ui.com/network-servers/<HOST_ID> (legacy) or locate it in UniFi Site Manager.

    • Validate by checking controller name, devices, last seen activity, or client identifiers.

  2. Remove / revoke access in UniFi (preferred)

    • In the UniFi portal, remove the MSP’s access or forget/remove the controller (exact wording varies by UniFi UI and permissions).

  3. Clean up in Liongard

    • In Admin → Discovered Systems, Archive/Ignore the discovered system if it should not be onboarded.

  4. Re-run / wait for next Parent inspection

    • Once access is removed on the UniFi side, the controller should stop appearing on subsequent discovery runs.

Archiving in Liongard helps reduce noise, but removing access in UniFi is what prevents future discovery.

Scenario B - Active client, but UniFi name is generic (e.g., “Default”) or not recognizable

If this is an active client controller/site and you want better identification:

Recommended actions

  1. Rename the site (where possible) in UniFi

    • Update the site name/description in the UniFi Network application so it’s not left as “Default”.

  2. Standardize naming in Liongard

    • When activating the discovered inspector, set a consistent Alias pattern (example): UniFi Network - <Client> - <Site>

  3. Document the mapping

    • Record Host ID / Site ID in internal documentation (or ticket notes) so future discoveries are easier to map.

  4. Check duplicates

    • If multiple entries appear as “Main Office”/“Default”, use the Edit (pencil) method in Discovered Systems to compare Controller URL / Host ID / Site ID and map each one correctly.

Scenario C - You can’t open the controller using the Host ID translation

If https://unifi.ui.com/network-servers/<HOST_ID> does not load the expected details:

Possible reasons

  • Your UniFi account doesn’t have permission to access that controller anymore.

  • The controller was removed/unlinked but still appears temporarily in discovery.

  • The controller is a modern UniFi OS console (and not a legacy network server).

  • The device is offline, decommissioned, or the UniFi UI behaviour differs for that tenant.

Next steps

  • Try locating it in the UniFi portal by browsing rather than searching by the Liongard alias.

  • Collect the Host ID / Controller URL / Site ID and contact Liongard Support (see below).

When to Contact Liongard Support 🦁

Contact Liongard Support if any of the following apply:

  1. You cannot identify which client/environment a discovered system belongs to after using:

    • Parent Inspector DataPrint method, and

    • Discovered Systems → Edit (pencil) method (Controller URL / Host ID / Site ID).

  2. The Host ID translation URL doesn’t work (e.g., unifi.ui.com/network-servers/<HOST_ID> fails) and you still need to map the system.

  3. Discovery appears inconsistent

    • Only some sites show proper names while others show super, domain/FQDN, or other generic identifiers.

  4. You suspect a product defect

    • Example: the same controller/site shows a friendly name in UniFi UI but Liongard consistently displays super or a hostname across multiple inspection runs.

  5. You see duplicated or conflicting discovered entries and cannot reliably map them using Host ID / Site ID.

What to include when opening a support ticket

Provide the following to speed up resolution:

  • Screenshot of the Discovered Systems row showing the alias

  • Values from Discovered System Edit (pencil):

    • Controller URL

    • Host ID

    • Site ID

  • Parent inspector DataPrint reference (timestamp) and the discovered object row (if possible)

  • Screenshots from controller showing the correct details (if applicable)

References 🌟

🚨 Note : We may occasionally provide links to third-party tools or resources for additional reference. These resources are offered for convenience only, and Liongard does not control, maintain, or guarantee their functionality, accuracy, or availability. Please review and use any third-party resources at your own discretion.

Did this answer your question?