When end-users report issues connecting to the Guest Wi-Fi or accessing the Splash Page, it can be tricky to determine the root cause. Generally, connection issues fall into one of two categories:
- Local Network Infrastructure Issues: Problems with your physical hardware, internet connection, or local network services (DHCP, DNS, VLANs, Firewall).
- Cloud4Wi Configuration Issues: Misconfigurations in the Cloud4Wi Dashboard or incorrect integration parameters on your Wi-Fi controller.
This guide will help you quickly isolate the issue so you can resolve it as efficiently as possible.
The "Quick Test": Where does the problem lie?
Before digging into complex configurations, you can run a simple test to immediately determine which of the two categories your issue falls into.
The Test: Connect a smartphone or laptop to your Guest Wi-Fi SSID and observe what happens.
-
Result A: You are redirected to a cloud4wi.com domain.
If your device automatically opens a browser (or a captive portal mini-browser) and loads a page whose URL ends in cloud4wi.com (for example, you see the Splash Page, or you see a Cloud4Wi error like the "Oops page"), your local network is working properly. This confirms your APs are broadcasting, DHCP is assigning IP addresses, and DNS is routing traffic.
👉 Conclusion: The issue is related to the integration or setup. Skip directly to Part 2. -
Result B: Nothing happens, or you get a generic browser error.
If you connect to the SSID but the portal does not pop up, or if you open a browser and see errors like "No Internet Connection," "Unable to obtain IP address," or "DNS Server Not Found," the redirect is failing at the local level.
👉 Conclusion: The issue is related to your local network infrastructure. Proceed to Part 1.
Part 1: Verifying Your Local Network Infrastructure
Because Cloud4Wi operates as an overlay on top of your existing network hardware, a healthy local network is an absolute requirement. If your network failed the "Quick Test," please perform the following checks.
How to test your local network:
We highly recommend creating an "Open" SSID (no captive portal, no splash page, no Cloud4Wi integration) assigned to the same VLAN as your Guest Wi-Fi to run these tests.
- Access Point Status: Are the Access Points (APs) powered on, broadcasting the SSID, and showing as "Online" in your hardware vendor's controller/dashboard?
- DHCP Assignment: Connect a device to the test SSID. Does it successfully obtain a valid IP address within the expected range for that VLAN?
- DNS Resolution: On the connected device, open a terminal/command prompt and try to ping a public domain (e.g., ping google.com). Does the domain resolve to an IP address?
- Internet Connectivity: Can the connected device successfully browse public websites?
- Firewall & Port Rules: Have you ensured that no local firewalls are blocking standard internet traffic on the Guest VLAN?
⚠️ Important Support Notice:
Cloud4Wi provides the guest Wi-Fi and authentication platform; we do not manage or have visibility into your local network hardware, ISP connections, or local routing rules. If any of the tests in Part 1 fail, the root cause resides within your local network infrastructure. Please work with your internal IT team, ISP, or hardware vendor to restore standard internet connectivity on your Guest VLAN before engaging Cloud4Wi Support.
Resume table | ||
|---|---|---|
| If the symptom is... | Likely Root Cause | Responsibility |
| SSID is not visible on mobile devices | AP Power / Radio configuration /Switch Power | Local Infra |
| Connected, but no Splash Page redirection |
|
Local Infra |
| Slow browsing after successful login | ISP Bandwidth / Airtime Congestion | Local Infra |
Part 2: Verifying Cloud4Wi Configuration
If you passed the "Quick Test" (your device is successfully redirected to a cloud4wi.com domain), your local network is functioning correctly. The issue is therefore related to a misconfiguration in the Cloud4Wi Dashboard or incorrect integration parameters (like Walled Garden, RADIUS, or Redirect URLs) on your Wi-Fi controller.
Our troubleshooting guides are organized based on the specific anomaly or error message you are experiencing.
Your Next Steps: Identify the exact symptom you are facing—for example, seeing the "Oops" error page, the Splash Page remaining blank, or a failure during the authentication process. Then, browse our Troubleshooting Section to find the dedicated article for that specific behavior. Each article will guide you through the exact configuration parameters you need to check to resolve the issue.
Need further assistance?
If you have verified that your local network is fully functional and you have reviewed the relevant troubleshooting guides but the issue persists, we are here to help!
When opening a support ticket, please include:
- Confirmation that you have tested DHCP/DNS and have internet access on the underlying VLAN.
- Confirmation that your device tries to redirect to the cloud4wi.com domain.
- The exact URL you are redirected to (please copy and paste the entire link).
- The brand and model of your Wi-Fi Controller/APs.
- Screenshots of your controller's Captive Portal and RADIUS configurations.