Answer first: Yes. Chrome does not block 10.0.0.1. Chrome’s new “Always Use Secure Connections” warning covers public websites only, and 10.0.0.1 is a private IP address, so it is excluded from the new warning. [Source: Google Blog, “HTTPS by default”; Chromium, “Ask-before-HTTP” adoption guide] If you see a warning at 10.0.0.1, it is one of the older messages in the table below — or you switched on Chrome’s stricter mode. Keep typing http://10.0.0.1 while connected to the vendo network.
Timing note (dated, do not delete): Google announced the new default for Chrome 154. [Source: Google Blog, 28 Oct 2025] Later Google Enterprise documentation and the Chrome 155 changelog put the all-users default in Chrome 155 [Sources: WindowsForum, 3 Oct 2026; AskVG, 7 Oct 2026], and the rollout is staged — two phones on the same version can behave differently. Check your own setting, not your version number. Last checked: 18 October 2026.
Which Message Are You Seeing?
Find your exact message in this table. Only one of these five is the new Chrome warning.
| Message | What it is | What to tap / do | New Chrome warning? |
|---|---|---|---|
| “This site doesn’t support a secure connection” — Continue to site / Return | The new Ask-before-HTTP warning. At 10.0.0.1 it appears only if you turned on the stricter mode. [Source: Chipp.in, 7 Oct 2026] | Tap Continue to site. Chrome remembers your choice for 15 days. [Source: Chromium adoption guide] | Yes |
| “Your connection is not private” — Advanced → Proceed to 10.0.0.1 (unsafe) | A certificate warning. You, or the browser, tried HTTPS against a server with no trusted certificate. This warning is years old. [Source: Chromium adoption guide] | Do not proceed on https://. Retype the full http://10.0.0.1. | No |
| “This site can’t provide a secure connection” (often with ERR_SSL_PROTOCOL_ERROR) | A TLS failure page. The browser tried a secure handshake and the portal does not speak TLS. | Retype http://10.0.0.1. If it still appears on http://, the problem is your network, not security — see the diagnostic below. | No |
| “Not secure” (next to the address) | A label on an HTTP page, not a block and not an error. | Nothing. The portal is HTTP by design. | No |
| “This site can’t be reached” / “took too long to respond” / “Connection refused” | A network failure. The browser never reached the vendo machine. | See Portal Won’t Load at All below. | No |
The one rule that separates all five messages
A warning page with buttons means the network path works — you are looking at a browser prompt, not a dead portal. No page at all means the browser never reached the vendo machine. That single distinction tells you whether to fix a browser setting or fix your connection.
What Changed in Chrome
Chrome’s “Always Use Secure Connections” setting tries every connection over HTTPS first. If a public website has no HTTPS, Chrome asks for your permission before the first visit, with two buttons: “Continue to site” and “Return”. [Source: Google Blog, “HTTPS by default”] The warning is bypassable, and Chrome remembers your decision for 15 days — if you visit the same HTTP site regularly, you may only ever see the warning once. [Source: Chromium adoption guide] You can switch the setting off at chrome://settings/security on desktop, or Settings → Privacy and security → Security on Android. [Source: Chromium adoption guide; Google Chrome Help, Android]
The new default covers public sites only
Private and local addresses are excluded: local IP addresses such as 10.0.0.1 and 192.168.0.1, single-label hostnames, and intranet names. [Source: Chromium adoption guide — “Non-unique hostnames, local IP addresses, and single-label hostnames will also not show warnings”]
Why no certificate can exist for 10.0.0.1
Private names are non-unique — the same address means a different machine on every network — so no single owner exists for a certificate authority to validate and issue a certificate to. [Source: Google Blog, “HTTPS by default”] Public certificate authorities may not issue certificates for private or reserved IP addresses. [Source: Let’s Encrypt community; https.in] That is why no public certificate can exist for 10.0.0.1, and why Chrome does not warn about it under the default.
One qualification that matters on Piso WiFi
Google’s reasoning for accepting private HTTP is that it “can only be abused by an attacker also on your local network.” [Source: Google Blog, “HTTPS by default”] On a Piso WiFi network, other customers are on that same local network. So treat the portal as a local page on a shared network, not as a page that is safe by definition.
On a Piso WiFi Portal
When you are paying or pausing on a Piso WiFi portal and a warning appears, match it to the table above first. Most of the time it will be the certificate warning, which means something tried HTTPS — the fix is retyping http://10.0.0.1, not changing a setting.
If you see the new warning at 10.0.0.1, you are in stricter mode
The new “This site doesn’t support a secure connection” warning at 10.0.0.1 means you are in Chrome’s stricter mode: “Warns you for insecure public & private sites.” [Source: Google Chrome Help, Android] Check it at Settings → Privacy and security → Security → Always use secure connections. Switch it back to “Warns you for insecure public sites” and the warning at 10.0.0.1 goes away. Android’s Advanced Protection turns the stricter mode on automatically, which is the most likely way a Piso WiFi user ends up seeing this warning. [Source: Google Chrome Help, Android]
Your pause time is not affected
Pause state lives in the vendo machine’s own database, tied to your device — not in the browser. [Source: businessmantalk.com, Piso WiFi pause-time guide] A browser warning cannot erase paused minutes. The real pause-time risks are the old ones: the pause limit expiring, or resuming from a different device. See also: Piso WiFi pause time · Chrome pause guide.
Stay safe at the portal
Proceed past a warning only when you are on the vendo network you intend, the address matches the machine’s sticker or instructions, and you are not entering banking or e-wallet credentials. Never enter bank or GCash credentials into the portal itself.
Why https://10.0.0.1 Fails
The https:// version fails because no publicly trusted certificate can exist for a private IP address, and the portal typically serves no TLS at all. [Sources: Google Blog, “HTTPS by default”; Let’s Encrypt community] There is one more rule that traps people: when you type https:// explicitly and it fails, Chrome does not fall back to HTTP — you get the certificate warning or a TLS error page, and you stay there. [Source: Chromium adoption guide] The fix is to retype the full http://10.0.0.1 address, including the http:// part. The same rules apply to the admin page at 10.0.0.1/admin — it is the same private address, so the same exclusion and the same https:// failure apply.
If It Flips http:// Back to https://
- Retype the complete
http://10.0.0.1address in a fresh tab. - Test in an incognito tab — that rules out a cached redirect from an earlier
https://visit. - Check whether the stricter mode is on (see On a Piso WiFi Portal above).
Do not use chrome://net-internals HSTS deletion for this: it is not verified for bare IP addresses, and retyping plus an incognito test solves the same problem.
Portal Won’t Load at All
Check in this order:
- Wrong network or mobile data on. Your phone routed to the internet instead of the vendo. Turn mobile data off and confirm the WiFi name matches the vendo machine.
- Typed into the search box, not the address bar. A search box gives you Google results, not the portal.
- Wrong gateway. Your vendo may use 192.168.1.1 or another address. Check the Gateway/Router in your WiFi details.
- VPN, Private DNS, or a data-saver switched on. Any of these can bypass or block the local gateway.
- Cached or stale page. Try an incognito tab.
- Vendo frozen or offline. Only the machine owner can restart it.
More login help: Piso WiFi login · Captive portal · 10.0.0.1 homepage.
Android vs Desktop
On Android
The “Sign in to network” popup opens the portal for you. If the popup never appears, type http://10.0.0.1 manually — that is the same destination, reached directly. Also check mobile data (it auto-switches away from a “no internet” WiFi), Private DNS, and VPN, which can all pull you off the local gateway.
On desktop
The same typed address works in any browser: connect to the vendo WiFi and type http://10.0.0.1 in the address bar.
Portal detection and iPhone
Chrome 154 does not change portal detection. No source found shows the new setting affecting the “Sign in to network” popup or captive-portal detection, so treat detection as unchanged. [Source: ugetfix, captive-portal background] On iPhone, Chrome 154 does not apply at all — it changes Chrome, not Safari. Use your phone’s normal Safari steps there.
Check It or Turn It Off
On desktop
Go to chrome://settings/security → Always use secure connections. [Source: Chromium adoption guide]
On Android
Go to Settings → Privacy and security → Security → Always use secure connections. [Source: Google Chrome Help, Android] There are two modes: “Warns you for insecure public sites” (the default) and “Warns you for insecure public & private sites” (the stricter one).
What not to do
Check your mode first before turning anything off. Switching the whole setting off also removes the warning on public websites, where it is actually protecting you. And do not “allow insecure content” for the portal as a workaround — you do not need to whitelist anything. The portal works on plain http://, and a global exception weakens your browser everywhere else for no benefit.
Frequently Asked Questions
Does Chrome block 10.0.0.1?
No. Chrome’s new warning covers public sites only. 10.0.0.1 is a private address and is excluded. [Source: Chromium adoption guide]
“Not secure” — am I hacked?
No. “Not secure” is a label telling you the page uses HTTP. The portal is HTTP by design. It is not a block and not an error.
How do I log in to 10.0.0.1 in Chrome?
Connect to the vendo WiFi, turn mobile data off, and type http://10.0.0.1 in the address bar — not the search box. See the full login steps on the homepage and the Piso WiFi login guide.
Does the warning appear on 10.0.0.1/admin too?
The same rules apply. /admin is the same private address, so the same exclusion and the same https:// failure apply.
Chrome 154 or 155 — which one?
Google’s documents disagree: the original announcement says 154 [Source: Google Blog, 28 Oct 2025], later Enterprise documentation and the 155 changelog say 155 [Sources: WindowsForum, 3 Oct 2026; AskVG, 7 Oct 2026], and the rollout is staged. Check your setting, not your version number.
Does this apply on iPhone?
No. Chrome 154 changes Chrome only. On iPhone, use Safari’s normal steps.
Is it safe to proceed past the warning?
Proceed only on the vendo network you intend, with the address matching the machine’s sticker or instructions, and never enter banking or e-wallet credentials into the portal.
I see the exact text “This site doesn’t support a secure connection” at 10.0.0.1. What does that mean?
It means you are in the stricter “public & private sites” mode. [Source: Google Chrome Help, Android] Tap “Continue to site” to proceed, then switch the mode back to “public sites only” in Settings.
Piso WiFi won’t load in Chrome at all — is this the Chrome update?
Probably not. If there is no warning page, the browser never reached the vendo. Run the diagnostic in Portal Won’t Load at All above — most cases are mobile data left on, the wrong gateway, or the address typed into the search box.
Sources
Last checked: 18 October 2026. URLs are given in full so they can be pasted as links.
Primary sources — read live, verified
- Google Blog, “HTTPS by default” (28 Oct 2025)
- Chromium, “Adapting your website for Chrome’s ‘Ask-before-HTTP’ warning”
- Chipp.in, “About Chrome’s error ‘This site doesn’t support a secure connection’” (7 Oct 2026)
- WindowsForum, “Chrome 154 or 155: When HTTPS-First Warnings Become Default” (3 Oct 2026)
- AskVG, “Google Chrome 155 Stable Released” (updated 7 Oct 2026)
- 10.0.0.1 admin homepage
Primary sources — cited from search-index snippet
- Google Chrome Help (Android), “Manage Chrome safety and security”
- Google Support, Chrome Enterprise “Previous release notes”
- Chrome for Developers, Chrome 154 release notes
Competitor pages checked — read live
- pisowifipausetime.org.ph, “Piso WiFi Login at 10.0.0.1”
- piso-wifi.org
- techpilipinas.com, “10.0.0.1 Piso Wifi”
- businessmantalk.com, “Piso WiFi Pause Time: 10.0.0.1 Login and Setup Guide”
- techdows.com, “10.0.0.0.1 Piso WiFi”
- 100001ip.mobi
Certificate rules — search-index snippets
- Let’s Encrypt community, “No CA can issue a Certificate for a PRIVATE IP Address”
- https.in, “SSL Certificate for IP Address”
Captive-portal background — search-index snippet
Maintenance: re-verify quarterly against the Chrome settings-page wording, the Chromium adoption guide, and Chrome Enterprise release notes. When the 154-vs-155 dispute settles, shrink the timing note to one dated sentence and keep the evergreen core (glossary, http-vs-https, stricter-mode check).