Piso WiFi Portal Shows Not Secure: What It Means and What to Do
If your browser shows Not Secure on a Piso WiFi portal, it does not automatically mean the portal is fake or that your money is already lost. It usually means the portal is served over local HTTP, not HTTPS, so the browser cannot verify it with a public certificate. That is normal for a local machine portal, and it is also the reason you must be careful about what you type into it.
This post covers only the Not Secure warning. It is not the general portal loading guide. If the portal will not open at all, go to the Portal Not Loading guide. If you paid and have no time, go to the No Internet After Paying guide or the Voucher Not Working guide, depending on how you paid.
Answer first: A Not Secure label on a Piso WiFi portal usually means the local portal is served over HTTP without a public certificate, not that it is automatically fake. Before you pay, confirm the exact WiFi name and the gateway shown on your own device, and do not enter bank, email, or social media passwords on the portal.
Part of Troubleshooting. Related: Portal Not Loading and No Internet After Paying.
What You Are Seeing
A Not Secure label, a “Not Private” warning, or a “Your connection is not private” page on a local portal usually has one of these meanings:
| What you see | What it usually means | What to do first |
|---|---|---|
| Not Secure in the address bar, but the portal opens | The portal uses HTTP on a local address, so there is no public certificate to check | Check the WiFi name and gateway first, then use the portal only for payment and time checks |
| A full warning page that blocks the page | Your browser is forcing HTTPS, or it found a certificate problem on a page that claims to be secure | Type the exact local HTTP address in the address bar, try an incognito window, and do not proceed past a certificate warning for a site you do not recognise |
| Not Secure on a page that asks for a bank login or a social media password | That page should never be trusted as a Piso WiFi portal | Stop, close the page, forget the network if you are unsure, and ask the operator to confirm the WiFi name |
A local Piso WiFi portal is not a public website. It lives on the machine network only, at an address such as http://10.0.0.1 or the gateway shown on your own device. A public certificate system cannot verify a private local address in the same way, which is why browsers label it Not Secure even when the machine is genuine.
Symptom Check: Is This the Right Portal?
Before you pay, answer these three questions. If any answer is no, stop and check with the operator.
1. Are you on the exact WiFi name for this machine?
A similarly named network nearby can show a similar portal. Check the WiFi name on your device against the sign on the machine or the name the operator gave you. If you joined a network with a slightly different spelling, forget it and join the correct one.
2. Did you type the gateway from your own device?
Open the Router field on iPhone, the Gateway field on Android, or the Default Gateway field on a laptop, and use that address. Do not guess, and do not use an address from a search result for a different machine. If the gateway on your device is not 10.0.0.1, use the gateway your device shows, as explained in the Portal Not Loading guide.
3. Does the portal match what the machine advertises?
Rates, payment options, and the machine location should match the sign or the operator’s description. A portal that asks for a bank login, a social media password, or a payment outside the portal, before any time is shown, is not a normal Piso WiFi payment step. Close it and report it.
Likely Causes, in Order
Cause 1: Local HTTP, no public certificate
This is the most common cause. The portal is served over HTTP on a local network, so the browser correctly notes that the connection is not encrypted in the public HTTPS sense. It does not, by itself, prove the portal is malicious, and it does not prove it is safe. It means you should limit what you enter.
Cause 2: HTTPS forcing by the browser
Some browsers or security settings try to upgrade a local HTTP address to HTTPS. The machine has no HTTPS page to upgrade to, so the browser may show a warning, a refused connection, or a loop. This is a browser setting problem, not proof that the machine is broken.
Cause 3: A stale redirect or cached secure page
A browser may remember a secure version of a page, or a redirect from an earlier session, and apply it to the local portal. That can turn a normal HTTP portal into a warning page. An incognito window, which starts without that saved state, is a useful test.
Cause 4: Wrong network or a rogue hotspot
A fake hotspot can copy the look of a real portal. This is less common than Cause 1, but it is the reason the symptom check above matters. If the WiFi name, location, rates, or payment steps do not match, treat the portal as untrusted, even if it looks convincing.
User Checks You Can Do Yourself
Work in this order, and test after each step.
- Confirm the WiFi name and the machine location, and forget any similarly named network you joined by mistake.
- Turn off mobile data and any VPN until the portal opens and the session starts, as a VPN can hide or redirect the local portal.
- Type the exact local address in the address bar, with http:// in front of it, not in the search box.
- Try an incognito or private window. If the portal opens cleanly there, the problem is cache, an extension, or a saved redirect in your normal window.
- Check Private DNS on Android and private relay on iPhone, and set them to Off or Automatic while you log in, if the portal still warns or loops.
- Do not enter banking details, email passwords, or social media passwords on the portal itself. The portal only needs a coin payment, a voucher code, or an e-wallet payment through the operator’s stated method, plus the pause and timer controls.
What You Should Never Do on a Not Secure Portal
- Do not log in to a bank, email, or social media account through a page that opened from the portal while you are unsure about the network.
- Do not proceed past a full certificate warning for a page that claims to be a well known secure site. A local portal warning and a warning for a bank site are not the same thing.
- Do not share an admin password, a voucher code in public, or a payment receipt in a public group to prove a problem. Show receipts only to the operator, in private.
Operator Checks, Labelled as Operator Only
Customers should not open a machine they do not own, and should not change portal security settings themselves. For the operator, the checks are:
- Confirm the machine WiFi name, gateway, and portal rates match the sign, so customers can tell the real portal from a copy.
- Check that the portal is reached by the local HTTP address, and that no setting is forcing customers to a secure public address that the machine cannot serve.
- Check for a stale portal redirect after a settings change, and test the portal as a customer on a phone that has never joined the machine before.
- Check whether a second network nearby is using a confusingly similar name, and rename the machine network clearly if needed.
- Keep firmware updated through the supplier’s official update path, as described in the Piso WiFi Software Update guide, and do not install a certificate or portal file from an unverified source.
Proof to Show the Operator
If you report a Not Secure problem, include:
- Machine location and WiFi name, exactly as shown on your device.
- A screenshot of the warning, including the address bar, if you can take one safely.
- Whether the warning appears on one device or on a second device as well.
- Whether the portal opened in an incognito window.
- What the portal asked you for, especially if it asked for anything other than a coin, voucher, or stated e-wallet payment.
Do not send banking passwords, social media passwords, or admin passwords with a report. A real operator does not need them to check a portal.
Prevention, for Users and Operators
For users, the habit that prevents most trouble is simple: confirm the network name before you pay, use the gateway from your own device, and treat the portal as a payment and timer page only. For operators, the habit is equally simple: keep the WiFi name clear, keep rates and payment steps on the sign, test the portal as a new customer after any change, and never ask customers for passwords or bank details through the portal.
Frequently Asked Questions About the Not Secure Warning
Does Not Secure mean my payment is already stolen?
No, not by itself. It means the browser cannot verify the local page with a public certificate, which is normal for a local HTTP portal. Check the WiFi name, gateway, and rates first. If anything does not match, stop and ask the operator before you pay.
Should I proceed past the warning to pay?
Proceed only if you have confirmed the exact WiFi name, the gateway from your own device, and the machine location, and the portal only asks for the normal coin, voucher, or stated e-wallet payment. If the portal asks for a bank or social media login, or the details do not match, do not proceed.
Why does my home WiFi not show Not Secure, but Piso WiFi does?
Home WiFi does not show a portal page in the same way. Piso WiFi shows a local portal page that the browser must label, because it is served over local HTTP without a public certificate. The label is about the page, not about whether your phone is connected to WiFi.
Is it safe to browse after I pay, if the portal said Not Secure?
Treat the network as a public network, as explained in the Safety guide. Casual browsing is generally fine, but avoid banking, password entry, or sensitive accounts on a public hotspot. A VPN for sensitive work, after the session starts, is a separate choice, and it can affect portal timer behaviour, so test it carefully.
The warning only appears on my phone, not on my friend’s phone. Is my phone broken?
Not necessarily. Browsers, browser versions, and security settings differ. One phone may force HTTPS while another does not, or one may have a cached redirect. Try an incognito window and the ordered checks in the Portal Not Loading guide before concluding the machine is at fault.
Can the operator make the portal show as secure?
A local machine portal cannot be made into a verified public HTTPS site in the same way as a public website, because it is a private local address. The operator can make it safer to identify by using a clear WiFi name, matching rates on the sign, and testing as a new customer, but customers should still treat it as a public network page.
What to Read Next
If the portal will not open at all, go to the Portal Not Loading guide. If the portal opens on one phone but not another, go to the Portal Loads on One Phone Not Another guide. If you paid and have no time, go to the No Internet After Paying guide. If you want the general safety rules for public WiFi, go to the Safety guide. If you are an owner who needs to change portal settings, go to the Admin Login guide.