Doesn't Support a Secure Connection with Https

You may see this while checking baby shoe sizes, first-shoe advice, or product details in Chrome: “This site doesn’t support a secure connection with HTTPS.” Chrome might also show “Your connection to this site is not secure” or a similar HTTPS not secure error.

The wording can feel alarming, but it usually points to one of two things:

1. A problem with your phone, computer, date and time, or browser settings.
2. A problem with the website itself.

That difference matters. You can fix some Chrome and device problems yourself. You can’t create HTTPS for a site that doesn’t provide it. Only the website operator can do that.

Here’s a simple way to work out which kind of problem you’re facing.

What “doesn’t support a secure connection with HTTPS” means

HTTPS is the protected version of a website connection. The extra “S” means the browser is asking for a secure connection before loading the page.

A site needs a TLS certificate for HTTPS. This is a digital certificate that helps Chrome check that the connection is meant to be secure. The website operator must get the certificate and set up the site to use it.

If the site has no working HTTPS setup, Chrome may say that the site doesn’t support a secure connection with HTTPS. You may also see:

• Your connection to this site is not secure
• Connection is not secure
• This site can’t provide a secure connection
• A warning near the address bar instead of the normal secure connection symbol

These messages are related, but they don’t always mean exactly the same thing.

A general “Your connection is not secure” warning can appear when Chrome has loaded a site without a protected HTTPS connection. It can also appear when Chrome’s secure-connection setting is turned on and the site doesn’t support HTTPS.

The more specific “doesn’t support a secure connection with HTTPS” message means Chrome tried to use HTTPS, but the site did not provide a usable HTTPS connection.

That may be a website problem. Still, check your own device first. A wrong clock or old browser data can sometimes make a working secure connection look faulty.

Check whether the warning appears on one site or every site

Start with the quickest test. Open another familiar website in Chrome.

If the warning appears on one site only, the website may be missing HTTPS or may have a problem with its secure setup. Your device is less likely to be the cause.

If the warning appears on many sites, check your device and browser. A wrong date, wrong time, or saved browser data can affect secure connections across several websites.

Try this small decision path:

• One site shows the warning: treat it as a possible website-side problem.
• Several sites show it: check date and time, then reset Chrome’s saved data.
• The site works on your phone but not your PC: compare the two devices. The PC may have a local Chrome, Windows, or time-setting problem.
• The warning appears only when you type `https://`: the site may not support HTTPS at all.

You can also try the same address in another browser on the same device. If it fails everywhere on that device, the issue may be with the computer or the website. If it fails only in Chrome, Chrome’s settings or stored data are more likely to be involved.

Don’t enter your name, address, card details, or other personal information while the warning is showing. You may still be able to read a page, but shopping and sign-in details should wait until the connection is secure.

Check your device’s date and time settings

Secure connections depend partly on the device having the right date and time. If your clock is far off, Chrome may have trouble checking a site’s TLS certificate.

This is a quick fix to try before changing anything else.

On an Android phone

Open your phone’s Settings and look for Date & time. The exact menu name can differ between Android phones.

Turn on the options that set the time and time zone automatically, if they’re available. Check that the displayed date, time, and time zone look right.

Then close and reopen Chrome. Try the website again.

On a Windows PC

Open Settings, then find the Time & language area and choose Date & time. Make sure Windows is showing the correct date and time.

Turn on automatic time and automatic time-zone options when available. If the clock was wrong, give Windows a moment to update it, then reopen Chrome.

This check is especially useful if:

• The warning started after the computer battery went flat.
• Your PC has been unused for a long time.
• Several websites show HTTPS warnings.
• The phone opens the site correctly but the computer does not.

If the date and time were already correct and only one site fails, move on. Don’t keep changing device settings when the problem is likely on the website’s side.

Reset Chrome’s saved security data and browsing cache

Chrome stores temporary website information. Windows also keeps an SSL state, which is saved information used when making secure connections. If this information is stale or damaged, clearing it can help Chrome try the connection again from a clean start.

This won’t add HTTPS to a website that has never supported it. It only helps with local browser data.

Clear the SSL state on Windows

On a Windows PC, search for Internet Options and open it. Choose the Content tab, then select Clear SSL state.

You may not see a big confirmation message. That’s normal. Close the window and restart Chrome.

The button clears saved secure-connection information in Windows. It doesn’t delete your saved passwords or remove the website’s own HTTPS setup.

Clear Chrome’s cached files

In Chrome on a computer:

1. Open the three-dot menu.
2. Choose Settings.
3. Open Privacy and security.
4. Choose the option for clearing browsing data.
5. Select cached images and files.
6. Clear the data, then close and reopen Chrome.

On Android, the names may be a little different:

1. Open Chrome.
2. Tap the three-dot menu.
3. Open Settings.
4. Find the privacy or browsing-data options.
5. Clear cached files, then restart Chrome.

You don’t need to remove everything. If Chrome lets you choose the type of data, start with the cache. Be careful with options that delete saved passwords or other sign-in information.

After clearing the cache, type the website address again rather than opening an old tab. If it loads securely, the issue was probably stored browser data.

If the same HTTPS warning returns on one particular website, that points back toward the site itself.

Review Chrome’s Always use secure connections setting

Chrome includes an Always use secure connections setting. When it’s enabled, Chrome tries to use HTTPS rather than opening a site through a less secure connection.

That setting is useful when a site supports HTTPS. It can also make the problem more visible when a site doesn’t.

When Always use secure connections is turned on and a website does not support HTTPS, Chrome can show a “Connection is not secure” warning instead of quietly opening the page.

To check the setting on a computer:

1. Open Chrome’s three-dot menu.
2. Select Settings.
3. Open Privacy and security.
4. Find Security.
5. Look for Always use secure connections.

On Android, open Chrome’s settings and look under the privacy and security options. The setting may appear in a slightly different place depending on your Chrome version.

You have two choices:

• Leave it on: Chrome will keep asking for secure connections and warn you when a site can’t provide HTTPS.
• Turn it off temporarily: Chrome may allow a site to open without HTTPS, but the connection still won’t be secure.

Turning the setting off does not fix the website. It only changes what Chrome asks for. Don’t use it as a reason to enter payment or personal details on a site showing a warning.

For shopping, account access, or anything involving private information, keeping the secure-connection setting on is the safer choice.

Steps for Android, Windows, and Chrome

The same website may behave differently on different devices. One reported situation had a site opening with HTTPS on an Android phone but failing to open as a secure HTTPS site on a PC.

That doesn’t prove the phone is safe or the PC is broken. It simply shows why testing the device matters.

If you’re using Android

Check these items:

• The phone’s date, time, and time zone.
• Chrome’s cached browsing data.
• Chrome’s Always use secure connections setting.
• Whether other websites open normally.

If other sites work and only one website shows the warning, stop changing phone settings after the basic checks. The site operator may need to fix its HTTPS setup.

If you’re using Windows

Check:

• Windows date and time.
• The saved SSL state through Internet Options.
• Chrome’s cached files.
• Chrome’s secure-connection setting.
• The same website in another browser.

If the site works on Android but not on your PC, resetting the SSL state and clearing Chrome’s cache are sensible next steps. Make sure Windows is fully showing the right date and time before trying again.

If you’re using Chrome

Restart Chrome after changing a setting or clearing saved data. Then open a fresh tab and enter the address again.

Chrome may use different wording depending on the type of connection problem. Don’t focus only on the exact sentence. Ask:

• Is this warning happening on one site or many?
• Does the address use HTTPS?
• Does the same address work on another device?
• Is Chrome asking for a secure connection that the site doesn’t provide?

Those answers usually tell you whether to keep troubleshooting or stop and wait for the website operator.

When only the website operator can fix the problem

A visitor can correct a wrong clock, clear saved browser data, and review Chrome’s settings. Those steps cannot install HTTPS on a website.

If the site itself doesn’t support HTTPS, the operator must:

1. Obtain a TLS certificate.
2. Install or connect it to the website.
3. Enable HTTPS on the site.
4. Make sure visitors are sent to the secure version.

Until that work is done, Chrome may continue to show a security warning. This is true even if your phone, computer, and browser are all working properly.

A site owner may also need to fix a certificate or server configuration if HTTPS works on one device but not another. That is still a website-side task once your basic device checks are complete.

If you’re trying to view baby footwear details, look for the same information on an official secure page or wait until the site operator fixes the connection. Don’t bypass the warning just to check a size chart, place an order, or submit contact details.

How to browse safely while the warning is displayed

A warning doesn’t always mean the page is harmful. It does mean Chrome can’t confirm the connection in the usual secure way.

You may choose to read general information, but keep the boundary clear:

• Don’t enter card or bank details.
• Don’t sign in with a password you use elsewhere.
• Don’t submit your address, phone number, or child’s personal details.
• Don’t download files from a page with a security warning.
• Don’t install anything because a warning page tells you to.
• Don’t turn off secure-connection checks simply to complete a purchase.

If the warning appears on every site, check the date and time first. Then clear Chrome’s cache and, on Windows, clear the SSL state. If the warning affects one site only, the operator probably needs to obtain a TLS certificate and enable HTTPS.

Once the connection is secure, you can continue to Baby Sock Shoe’s sizing and first-shoe guides with more confidence—without bypassing Chrome’s warning.