Use this article when guests on a Cisco Meraki network see the captive portal of another site, are recognized as being in the wrong location, or get an error message such as "Wrong passcode".
Which case applies?
- The portal or the location is not the expected one: steps 1, 2, and 3.
- An error message appears when guests join an event: steps 1 and 4.
- A generic error page appears instead of the portal: see There is an error page instead of the captive portal.
Prerequisites
Before starting, ensure that you have the following prerequisites:
- Access to Cloudi-Fi's admin console
- Access to the Cisco Meraki dashboard
- A test device connected to the affected guest SSID
1. Collect the on-site information
The issue is usually specific to one location. Note the following during a test on site:
- The date and time of the test, with the time zone
- The MAC address and IP address of the test device. Devices can use a private MAC address per SSID, so read the address shown in the Wi-Fi settings of the device for this SSID.
- The name or MAC address of the access point (AP) used
- A screenshot of the portal or of the error message
Then run the same test from Cloudi-Fi:
- In the Cloudi-Fi admin console, open "Locations".
- At the end of the line of the affected location, click the three-dot button and select "Try portal".
- Check that the expected portal opens, and complete the authentication.
Compare both results:
- "Try portal" shows the right portal, but the on-site test does not. The location is correct in Cloudi-Fi, and the issue is in the link between the AP and the location. Go to step 2.
- "Try portal" shows the same issue. The issue is in the location settings or in the event. Go to step 4 for an event error, or contact support.
2. Check the splash page URL
- In the Cloudi-Fi admin console, go to "Configuration" > "Integrations" > "Meraki". Click the three-dot button, select "Configure SSIDs", open the "Manual" tab, and copy the splash page URL.
- In the Meraki dashboard, go to "Wireless" > "Configure" > "Splash page" (or "Security & SD-WAN" > "Configure" > "Splash page" for MX). Select the SSID and compare the "Custom splash URL" with the URL from Cloudi-Fi.
The URL has four parts:
https://login.cloudi-fi.net/start/ch/<tenant ID>/lh/<location ID>/sp/spmeraki.com
-
https://login.cloudi-fi.net/start/is the Cloudi-Fi domain. -
ch/<tenant ID>is the tenant of the customer. -
lh/<location ID>identifies the location. The value is set in the "Network Parameters" tab of the location. It can be a hash, a MAC address, an IP address, or a name. -
sp/spmeraki.comis the vendor integration.
Check each part:
- The location ID must match the "Network Parameters" tab of the expected location. An ID copied from another site, or the identifier of an AP that was removed or replaced, sends guests to the wrong location.
- The vendor integration must be
spmeraki.com. This matters in a tenant with several vendor integrations, where another vendor can be the default.
If the URL differs, replace it with the URL from Cloudi-Fi. Do not edit identifiers by hand. See Splash page configuration update for Meraki's captive portal.
3. Check the AP and the location
- In the Cloudi-Fi admin console, edit the expected location and open the "Network Parameters" tab.
- Check that the MAC address of the AP used for the test is listed in this location only.
- If the AP is missing or listed in another location, see Cisco Meraki networks, locations, or access points are missing in Cloudi-Fi.
- Repeat the test with the same device, and compare with the result of step 1.
4. Check an event error message
When guests cannot join an event, for example with a "Wrong passcode" message, check the following in the event settings:
- The validity period of the event. The test must fall within the start and end dates.
- The passcode. Compare it with the one given to guests, including letter case.
- The locations assigned to the event. The affected location must be in the list.
If the same event works at another site, compare the settings of both locations. For more detail, see How to create and launch an event for a location.
5. Check the URL of the error message
There may a case where the URL error contains the following URL: network-auth.com
This URL belongs to Meraki and we would suggest you to open a case with Meraki Support.
Contact your support
If the issue remains, contact the Cloudi-Fi support team and share the following information:
- The SSID name and the Cloudi-Fi location
- The Meraki Network name
- The name or MAC address of the access point used
- The date and time of the test, with the time zone
- The device model and operating system
- The device Mac Address and IP address
- The authorization status of the device in the Meraki dashboard
- The event name, if an event is involved
- The splash page URL configured in Meraki
- Screenshots of the issue and the result of "Try portal"
- A HAR file of the failing connection: web browser, Android, or Apple iPhone and iPad
Never share an event passcode in a screenshot.
What's next?