Occasionally, Access Points (APs) in your network may be configured to route traffic through Cloud4Wi (using RADIUS and captive portal configurations) but have not yet been provisioned in your Cloud4Wi account inventory.
Common causes for this discrepancy include:
Configuration Errors: An AP was configured by mistake, often occurring during bulk configurations or when applying configuration templates.
Hardware Changes: An AP was replaced or newly installed, but the administrator forgot to register the new hardware identifier in the Cloud4Wi platform.
The Impact of Unmapped APs
By default, any AP that is not explicitly provisioned in your Cloud4Wi account will block users from being authorized on the network.
Captive Portal: Users connecting to a hotspot will be redirected to an error page ("Oops page").
Silent Authentication: Protocols such as MAC authentication, Passpoint, or 802.1x will result in the RADIUS server rejecting the authorization request.
Prerequisites for Detection
Cloud4Wi can automatically detect these unmapped APs to help you resolve network anomalies. To enable this detection, your network must be configured with tenant-specific parameters rather than legacy global settings.
Ensure your network is using the following:
Tenant-Specific Splash Page URL:
Navigate to General Settings > WiFi Settings.
Note: If you are still using the legacy URL (
splashportal.cloud4wi.com), you must update your configuration to the tenant-specific URL found in your settings.
Tenant-Specific RADIUS Ports and Secret:
Navigate to General Settings > WiFi Settings.
Note: If you are using the legacy RADIUS server, please refer to the upgrade guide to switch to the tenant-specific configuration.
Pro Tip: Once you have updated your configuration, you can enable "Fallback Experience Mode." This ensures that users connecting to an unmapped AP are not blocked, but instead receive a fallback experience while you resolve the configuration issue. [Learn more about Fallback Experience here].
Locating Unmapped Access Points
Cloud4Wi logs all APs that attempt to connect but are not in your inventory. To view these devices:
Navigate to Manage > Access Points.
Click the Unmanaged Access Points button at the top of the page.
The table provides detailed insights into these devices:
Identifier: The name or ID reported by the Access Point.
MAC Address: The unique hardware identifier of the device.
First Seen: The timestamp of the very first user connection attempt on this AP.
Last Seen: The timestamp of the most recent interaction with the Cloud4Wi service.
Fallback Experience: (Visible only if Fallback Experience is enabled)
Active: The AP is currently providing a fallback experience to users (within the 30-day limit).
Blocked: The 30-day fallback period has expired, and the AP is no longer authorizing users.
Resolving the inventory anomalies
You have two options for handling unmapped APs:
1. Add the AP to your Inventory If the AP is a legitimate part of your deployment:
Click the Menu icon next to the specific AP in the list.
Select the option to Add to Inventory.
Follow the on-screen instructions to provision the device.
2. Remove the Configuration If the AP was configured by mistake:
Remove the Cloud4Wi configuration (RADIUS/Splash Page settings) from the physical Access Point itself.
Automatic Cleanup: Once the configuration is removed and the AP stops sending requests to Cloud4Wi, the system will automatically remove the entry from the "Unmapped Access Points" table after 30 days of inactivity. In the alternative, you can click the option Delete form the Action dropdown menu for that access point to remove it form the table right away
For APs that are currently providing a Fallback Experience (status: Pending), you can revoke this access immediately.
Select Block Fallback Experience from the Action menu.
This stops the AP from delivering network access to users, even if the 30-day allowance has not yet expired.