Can't reach this page

Ralph Garcia 0 Reputation points
2026-09-25T15:31:52.74+00:00

going to secure website error message is ERR_CONNECTION_TIMED_OUT using windows 11

Microsoft Edge | Website issues | Windows 11
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. EmilyS726 271.2K Reputation points Independent Advisor
    2026-09-25T16:05:51.16+00:00

    Can you share the URL for "this" page?

    Is the error only given to this particular URL? Other URL works fine?

    What about browser? Does it matter which browser you are using?

    Was this answer helpful?

  2. AI answer

    2026-09-25T15:32:07.8933333+00:00

    For a secure website timing out on Windows 11, use this order of checks:

    1. Try the site in Microsoft Edge and make sure Edge is updated.
      In Edge, go to Settings and more > Settings > About Microsoft Edge. If an update is available, install it.
    2. Clear cached browsing data in Edge.
      Go to Settings and more > History > Open history page > Delete browsing data. Select All time, choose Browsing history and Cached images and files, then select Clear now.
    3. Restart the PC and test the site again.
    4. Check whether the problem is specific to one device.
      Try connecting another PC to the same network. If the other PC can reach the site, the issue is likely on the original Windows 11 device. If neither device can connect, the issue may be with the router, ISP, or network path.
    5. Run a network reset as a last step.
      In Windows 11, go to Start > Settings > Network & internet > Advanced network settings > Network reset > Reset now > Yes. Warning: Network reset removes installed network adapters and resets network settings to defaults. After restart, VPN software or virtual switches such as Hyper-V networking may need to be reinstalled or reconfigured. Known networks may also be set back to Public.

    If the site works over HTTP but fails only over HTTPS, one documented cause is a website certificate using an RSA key smaller than 1024 bits. If the site is hosted on IIS, another documented cause is that the bound certificate does not have a matching private key.

    Internet Explorer 11 is retired and out of support. If this issue is being tested there, use Microsoft Edge instead.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.