Portal Not Loading on Piso WiFi: The Ordered Checklist, Plus Android, iPhone, and Laptop Fixes

A portal that will not load is not the same as no internet after paying. In this problem, you cannot reach the payment page at all, so you should not pay yet. Work through this checklist in order, and test after each step. Changing five settings at once makes it impossible to know which change helped, and it can create a new problem while you are fixing the first one.

This post also covers the merged Connected but No Internet device sections. That problem is included here, in the device sections below, because its fix checklist is the same as the portal checklist, with device settings as the only difference. There is no separate Connected but No Internet post.

For a portal that opens but shows no timer after payment, go to the No Internet After Paying post. For a device stuck on Obtaining IP Address, go to the Obtaining IP Address post. For full login steps once the portal opens, go to the Login pillar.

Before You Start: Confirm You Are on the Right Network

Check the WiFi name in your device settings, not just the WiFi icon. You must be connected to the exact network name of the machine you intend to use. A phone can join a saved home network, a neighbouring hotspot, or a network with a similar name, and then no portal for the intended machine will appear.

If you are not on the right network, forget the wrong network for now, join the correct one, wait a few seconds, and then open a browser. Do not type a payment address or a gateway address while you are still on the wrong network.

The Ordered Checklist

Work from top to bottom. After each step, open a browser and try the portal address in the address bar, with http in front of it, for example http://10.0.0.1, or the gateway address shown in the Router or Gateway field on your device if it is different.

Step 1: Use the address bar, not the search box

Typing an address into a search box runs a web search, which fails because you are not yet online. Type it into the address bar at the top of the browser. On a phone, the address bar may be hidden until you tap the top of the screen. Make sure you are typing into the browser address field, not into a search widget on the home screen.

Step 2: Turn off mobile data

Turn off mobile data until the portal opens and a session starts. A phone on mobile data can skip the WiFi portal completely, because the phone already has an internet path. This is the most common reason a portal never appears, even though WiFi shows as connected.

Step 3: Turn off VPN and private relay

Turn off any VPN, including one that starts automatically, until login succeeds. Turn off private relay on iPhone if it is on. A VPN or relay can route traffic away from the local portal and hide it. You can turn a VPN back on later for sensitive work, after the session starts, but check that the timer still works.

Step 4: Try an incognito or private window

Open the portal in an incognito or private window, with VPN off and mobile data off. If the portal loads there but not in your normal window, the problem is a stale cached page, an extension, or a saved redirect in your normal window, not the machine. Clear the cache for that page, or continue in the private window for this session, and do not enter banking details on the portal itself.

Step 5: Check Private DNS on Android, and Private Address on iPhone

On Android, set Private DNS to Off or Automatic while you log in. A Private DNS hostname can block the local portal. On iPhone, check the Private WiFi Address setting for that network, and the private relay setting in Step 3. Do not change the private address setting in the middle of a paid session, because that can make the machine treat the same phone as a new device. Change it before you pay, if you are troubleshooting a machine that repeatedly fails to recognise your device.

Step 6: Check https forcing and security warnings

The portal is a local page served over http in the usual case, not https. A browser setting that forces https, or a security setting that blocks http pages, can stop the portal from loading and can show a connection is not private warning. Use http in front of the address, in an incognito window, for the portal test. Do not ignore a warning on a banking or email site, but do not confuse a local portal http warning with a warning on a public secure site.

Step 7: Check the gateway address, do not guess

Most machines use 10.0.0.1, but some use a different gateway set by the operator. Find the correct address from the Router field on iPhone, the Gateway field on Android, or the Default Gateway field on a laptop. If you type the wrong gateway, you will get nothing, or you will open a different local device. Do not guess gateway addresses, and do not add extra digits. A common typing error is an extra zero, which gives a different address that will not load the portal.

Step 8: Test a second device

If the checklist above fails on one device, test a second device on the same machine, with mobile data off and VPN off, in an incognito window. If the second device opens the portal, the problem is specific to the first device, and the device sections below are the next step. If the second device also fails, the problem is more likely the machine, its portal, or its power and network, and you should report it to the operator rather than changing more device settings.

Step 9: Check for the admin address by mistake

The plain address is the customer portal. The address with /admin at the end is the admin panel for owners. If you open the admin address by mistake, you will see a username and password page, not a payment page. Go back to the plain address. Owners who need the admin panel should use the plain address plus /admin, while connected to the machine network, and follow the Admin Login guide.

Connected but No Internet: What It Means, and What to Do Next

This section is the merged device coverage for Connected but No Internet, because its fixes are the device fixes above, applied in a specific order.

Before login, this message is often normal

On a captive portal network, Connected, no internet often means the phone is connected to WiFi but is waiting for portal login before full internet access is allowed. Open the portal, pay, and check the timer. Do not treat this message alone as proof that the machine is broken.

After login, this message means something else

If the message remains after payment, and the timer is running, the problem is no longer portal access. It is browsing, ISP, machine, or speed. Go to the No Internet After Paying post, and run its browsing test, rather than repeating the portal checklist. If the message remains and the timer is not running, return to Step 1 above, because the session did not start.

If the message appears only on one device

Work through the device section for that device below, in order, and test after each change. Do not reset the machine, and do not pay again until the portal opens cleanly on that device.

Android Fixes, in Order

1. Turn off mobile data, and turn off any VPN.
2. Set Private DNS to Off or Automatic for the login test.
3. Forget the network, rejoin it, and open the portal in an incognito window.
4. Check WiFi sleep and battery saver settings that turn WiFi off when the screen locks. Keep WiFi on during a session.
5. Check the Gateway field for the correct portal address, and type it into the address bar with http in front of it.
6. If the portal still fails, test a second device. If the second device works, the fault is in the first device settings or browser, not the machine.

Who can fix it: steps 1 to 5 are user fixes. Step 6, if both devices fail, is an operator fix, usually a portal restart from the admin panel.

iPhone Fixes, in Order

1. Turn off mobile data, and turn off any VPN and private relay.
2. Check the Router field for the correct portal address, and type it into the address bar with http in front of it, in a private window.
3. Forget the network, rejoin it, and open the portal again.
4. Check the Private WiFi Address setting for that network, and do not change it mid session. If you changed it after paying, tell the operator when you report the problem.
5. Check that the phone has not switched to mobile data while locked. Keep WiFi on during a session.
6. If the portal still fails, test a second device. If the second device works, the fault is in the first device settings or browser, not the machine.

Who can fix it: steps 1 to 5 are user fixes. Step 6, if both devices fail, is an operator fix.

Laptop and PC Fixes, in Order

1. Confirm you are connected to the correct WiFi name, and that mobile data tethering or a VPN is off.
2. Open a browser, not a search widget, and type the portal address into the address bar with http in front of it.
3. Try an incognito or private window. If it works there, clear cache or disable extensions in the normal window for the portal test.
4. Check the Default Gateway field for the correct portal address, if the usual address does not load.
5. Check that a security tool, firewall, or browser setting is not forcing https or blocking local http pages for this network.
6. If the portal still fails, test a second device. If the second device works, the fault is in the laptop browser or network settings, not the machine.

Who can fix it: steps 1 to 5 are user fixes. Step 6, if both devices fail, is an operator fix.

When the Problem Is the Machine, Not Your Device

Report it to the operator, rather than changing more settings, if any of these are true: the portal fails on two devices with clean browsers, mobile data off, and VPN off; the portal loads on one device but redirects in a loop on a clean second device; the machine has no power, keeps rebooting, or the portal was working earlier today and stopped for everyone at the same time.

Give the operator: machine location and WiFi name, device types tested, what you tried in order, the gateway address you used, and whether other customers are affected. Do not send banking passwords, social media passwords, or admin passwords. A real operator does not need those to check a portal.

Do not restart a machine you do not own, and do not open the machine box. A portal restart from the admin panel is an operator step, after noting rates and settings, because a restart can clear local sessions.

Frequently Asked Questions About Portal Not Loading

Why does the portal open on my friend’s phone but not on mine?

Because the fault is usually in the first device settings or browser, not the machine. Work through the device section for your phone, in order, with mobile data off and VPN off, and test in an incognito window. If your friend’s phone works on the same machine, the machine portal is running.

I typed the portal address, but I got a search results page. What went wrong?

You typed it into a search box, not the address bar. Open a browser, tap the top of the screen to show the address bar, type the address there with http in front of it, and try again.

The portal shows a not private warning. Should I proceed?

For a local portal over http, that warning is expected in many browsers, because the local page is not a public secure site. Use an incognito window for the portal test, and do not enter banking details on the portal itself. Do not apply the same reasoning to a banking, email, or payment site, where a not private warning should stop you.

I turned off my VPN, but the portal still will not load. What next?

Work through the next steps in order: incognito window, Private DNS or private relay check, gateway address check, and forget and rejoin. Do not turn the VPN back on and retry the same failed step, because the VPN may not have been the only blocker.

Connected, no internet appears before I pay. Is that an error?

Usually, no. On a captive portal network, that message often means the phone is waiting for portal login. Open the portal, pay, and check the timer. If the message remains after payment with a running timer, go to the No Internet After Paying post.

The portal keeps redirecting in a loop. Is that my phone?

Test in an incognito window with VPN off, on a second device if you can. If the loop happens on two clean devices, tell the operator, because the machine portal may need a restart from the admin panel. Do not keep reloading the same loop, and do not pay until the portal opens cleanly.

Portal Refresh Loops, Typo Variants, and Gateway Variants

If the portal refreshes in a loop or never finishes loading, clear the browser cache and try a fresh incognito page, and check https forcing again, because a browser that forces https can return a connection refused error on a local http portal. Check the typed address character by character. Common typos are an extra zero, a space in the address, and a lowercase letter L typed instead of the digit 1. Do not force 10.0.0.1 if your device shows a different gateway. Check the gateway field on your own device, and use the gateway it shows, because some builds use a variant such as 10.10.0.1. If the gateway field is empty, or if several customers have the same loop, the cause is more likely DHCP lease exhaustion, an IP conflict from a secondary router or extender, or a machine fault, and the operator needs to check it.

What to Read Next

If the portal opens but browsing still fails after payment, go to the No Internet After Paying post. If a device is stuck on Obtaining IP Address, go to the Obtaining IP Address post. For full login steps once the portal opens, go to the Login pillar. For the general diagnostic method, go to the Troubleshooting pillar. For pause problems after a drop, go to the Pause Time pillar.