Share via

how to prevent W10 blocking HTTP (unsigned) on your own private network

Khunmoo2 16 Reputation points
2026-03-07T07:52:48.8633333+00:00

Need to access device internal browser in a NAS device but the browser blocks access to http URL on local network

Windows for home | Windows 10 | Internet and connectivity
0 comments No comments

2 answers

Sort by: Most helpful
  1. Sumit D - IA 165.4K Reputation points Independent Advisor
    2026-03-07T09:21:25.5733333+00:00

    Hi Khunmoo,

    Could you please try this:

    • • Open Microsoft Edge.
    • • Type edge://flags/#edge-automatic-https in the address bar and press Enter.
    • • Set Automatic HTTPS to Disabled.
    • • Open edge://net-internals/#hsts in the address bar.
    • • Under Delete domain security policies, enter the domain name in the Domain field.
    • • Press Enter to remove the policy.

    #2:

    • Open edge://settings/clearBrowserData.
    • Set Time range to All time.
    • Select Cached images and files and Browsing history.
    • Click Clear now.
    • Open edge://settings/content/insecureContent.
    • Under Allow, click Add.
    • Enter the domain name and save.

    Close and restart Microsoft Edge.

    I’m eager to hear back and work together to find a solution.

    0 comments No comments

  2. Q&A Assist
    2026-03-07T07:53:01.6466667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    In Microsoft Edge on Windows 10, access to HTTP (non‑HTTPS) devices on a private network can be affected by the Local Network Access feature and related enterprise policies. To allow access to an internal NAS web interface over HTTP on the local network, adjust Edge’s Local Network Access behavior and, if managed, check that no blocking policies are applied.

    1. Enable Local Network Access checks and allow prompts
      1. In Edge, go to edge://flags/#local-network-access-check.
      2. Set Local Network Access Checks to Enabled (not Enabled (Blocking)).
      3. Select Restart in the lower-right corner.
      4. After restart, open Settings and more (⋯) > Settings.
      5. Go to Privacy, search, and services > Site permissions > All permissions.
      6. Scroll to Local network access.
      7. Turn on Ask before accessing (recommended).
      8. When browsing to the NAS HTTP URL, allow the prompt so the site can reach local devices.
    2. If the device is managed by an organization, verify Edge policies On managed PCs, administrators can centrally block or allow Local Network Access for specific public sites. If a policy is blocking access, it must be changed by the admin. Relevant policies:
      • LocalNetworkBlockedForUrls – blocks sites from making network requests to local network endpoints.
      • LocalNetworkAccessBlockedForUrls – blocks sites from issuing Local Network Access requests.
      • LocalNetworkAccessAllowedForUrls – allows sites to make network requests to local devices and local network endpoints.
      On Windows, these are configured via Group Policy or registry:
      • Group Policy paths (for admins):
        • LocalNetworkBlockedForUrls: Administrative Templates/Microsoft Edge/Local Network Access settings
        • LocalNetworkAccessBlockedForUrls: Administrative Templates/Microsoft Edge/Network settings
        • LocalNetworkAccessAllowedForUrls: Administrative Templates/Microsoft Edge/Network settings
      • Registry locations (for admins):
        • SOFTWARE\Policies\Microsoft\Edge\LocalNetworkBlockedForUrls
        • SOFTWARE\Policies\Microsoft\Edge\LocalNetworkAccessBlockedForUrls
        • SOFTWARE\Policies\Microsoft\Edge\LocalNetworkAccessAllowedForUrls
      If a wildcard like * or a pattern matching the site that is used to reach the NAS is present under a BlockedForUrls key, that origin will be prevented from accessing local network endpoints. Removing or adjusting that entry, or adding the origin to LocalNetworkAccessAllowedForUrls, will permit access according to the precedence rules:
      1. LocalNetworkBlockedForUrls
      2. LocalNetworkAllowedForUrls
      3. LoopbackNetworkAccessBlockedForUrls
      4. LoopbackNetworkAccessAllowedForUrls
      5. LocalNetworkAccessBlockedForUrls
      6. LocalNetworkAccessAllowedForUrls
      For origins not covered by these policies, the user’s own Local Network Access configuration (step 1) applies.

    Once Local Network Access is set to prompt/allow and no blocking enterprise policy applies to the origin used to reach the NAS, Edge will no longer block HTTP access to that device on the private network.


    References:

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.