On iOS the warning is usually the network, not the site: hotel, airport and café Wi-Fi intercept HTTPS at the captive portal before you have signed in.
On iOS the warning is usually the network, not the site: hotel, airport and café Wi-Fi intercept HTTPS at the captive portal before you have signed in.
Open any plain http:// address to force the sign-in page, complete it, then reload. If the warning appears on mobile data too, the certificate itself is the problem.
iPhone has its own failure mode, but Your connection is not private has a wider set of causes. The most common one overall is: The certificate expired (NET::ERR_CERT_DATE_INVALID).
Renew the certificate and reload the web server.
Running the check from outside your device separates a real certificate problem from a local clock or network issue in one step.
On iOS the warning is usually the network, not the site: hotel, airport and café Wi-Fi intercept HTTPS at the captive portal before you have signed in.
Open any plain http:// address to force the sign-in page, complete it, then reload. If the warning appears on mobile data too, the certificate itself is the problem.
Chrome's full-page warning shown whenever certificate validation fails. It is not a single error — the real cause is the NET::ERR_CERT_* code printed underneath it, and that code tells you which of expiry, trust, or hostname is wrong.