Purpose
Use this when a UniFi wireless network appears to have vanished from client Wi-Fi scans even though the WLAN still exists in the controller.
The useful question is whether the SSID is actually gone from the AP, or whether the AP is still transmitting the WLAN while suppressing the SSID name.
This path was validated on UniFi Network 6.5.55 with UAP-AC-PRO access points. The same logic is useful on other UniFi versions, although menu names and provisioning behavior can differ.
Diagnostic procedure
- In UniFi, open Settings > Wireless Networks and confirm the affected WLAN still exists and is enabled.
- Check the WLAN's Broadcasting APs setting. Confirm the selected option actually contains APs. Do not assume that an empty AP group shown in the UI is selected merely because it is listed.
- Open an AP that should advertise the WLAN and inspect its WLANs section.
- If the expected ESSID is present on one or both radio interfaces, the controller has provisioned that WLAN onto the AP.
- If the AP is also advertising other SSIDs normally, basic AP adoption, uplink, and radio operation are likely healthy.
- Separate SSID visibility from VLAN or connectivity troubleshooting. A VLAN or DHCP problem normally becomes relevant after a client associates. If the SSID name itself is absent from scans, first investigate WLAN broadcast settings.
- On a nearby Windows client, inspect available networks. For a more detailed scan:
netsh wlan show networks mode=bssid
- If Windows shows a generic Hidden Network, attempt to connect to it manually using the expected SSID name and the existing wireless credentials.
- If the connection succeeds and Windows then shows the expected SSID as Connected, secured, this is strong validation that:
- the WLAN is still being transmitted
- authentication is working
- the SSID name is being hidden rather than the WLAN being absent
- In UniFi, return to Settings > Wireless Networks > [SSID] > Edit > Advanced Options and inspect Hide SSID / Prevent this SSID from being broadcast. If it is enabled unintentionally, uncheck it and apply the change.
Validation
After changing Hide SSID:
- rescan from a nearby client and confirm the SSID now appears by name without manually joining a hidden network
- confirm a test client can associate normally
- verify it receives the expected IP configuration and can reach the required network resources
- confirm other production SSIDs and clients recovered normally after any AP reprovisioning
If the change produces unexpected behavior, restore the previous Hide SSID setting and apply the WLAN configuration again. Capture the original setting before changing it so the rollback state is unambiguous.
Catches / gotchas
- The AP WLAN list can show the configured ESSID even when the SSID name is hidden from normal client scans. Treat that list as evidence that the virtual WLAN is provisioned, not proof that the SSID name is visible.
- An unexpected or missing same-named object under Settings > Networks can be distracting. Do not treat that alone as the cause of a missing SSID if a client can associate to the WLAN as a hidden network.
- A hidden SSID can look like a total WLAN outage to users or devices that rely on normal network discovery, even while previously configured or manually configured clients can still connect.
- On older UniFi controller and AP generations, applying a WLAN configuration change can reprovision the APs and briefly disassociate wireless clients. If the WLAN is broadcast by many APs or supports operational devices, make the change during a quiet window. Do not assume only the edited SSID will be affected.
Key lesson
When a UniFi SSID disappears from ordinary Wi-Fi scans but the controller and AP still show the WLAN, test it as a hidden network before investigating VLANs, DHCP, switching, or recreating the WLAN. A successful hidden-network connection sharply narrows the problem to SSID advertisement rather than a full wireless outage.