Linking to a url that is only available on internal server?

[YvanMartino]

We have knowledge articles that point to internal resources (not accessible except when on the local network or when connected via VPN)

Is there anyway to allow for the urls to redirect cleanly, without having the user right-click to open a new tab.

Currently we're running into the message "The connection is blocked because it was initiated by a public page to connect to devices or servers on your local network."  Which I think we're getting because ServiceNow is trying to handle the url on the server-side before redirecting.

[Tanushree Maiti]

Hi @YvanMartino ,

If it client instance, 

Ensure you are not trying to access an internal  site which is not approved by your client.

1. Clear your cache and cookies to ensure outdated security rules aren't being applied.

2. Upgrades to Chrome v142/Edge v143 restrict public-to-private navigation.

3. Ensure any firewall rule or Zscaler is not causing the issue

4.Lastly check your Local Network access: 

In Chrome, go to settings and look for Privacy and Security > Site Settings > Additional permissions > Local network access to ensure sites are not being blocked from local devices., 

(it it is blocked in your system)

  Refer:  https://support.google.com/chrome/thread/386057056/local-network-access-setting-in-new-chrome-versio...

Troubleshooting Local Network Access:

When Chrome restricts local network access, it often requires the target local device to explicitly allow the connection via a "preflight" check.

1. Is there another setting? (Server-Side)

Often, the missing "setting" is not in Chrome, but on the local server you are trying to reach. The local resource must be configured to respond to a CORS preflight request with specifically required headers, such as:

Access-Control-Allow-Private-Network: true

If the local device cannot be updated to send these headers, Chrome may still block the request to protect your network, regardless of the allowlist policy.

2. Verify Policy Application

Ensure the policy is applied correctly to the initiating public website, not just the target local IP.

• Open chrome://policy in your address bar.
• Click Reload policies.
• Verify that LocalNetworkAccessAllowedForUrls is listed, Status is "OK", and the value matches exactly the origin (e.g., https://your-trusted-website.com) that is trying to connect to your local network.

3. Check Developer Tools for Specific Errors

To confirm if it is a policy failure or a CORS failure:

• Press F12 to open Developer Tools on the page that is failing.
• Click the Console tab.
• Look for red errors. A message mentioning "Preflight" or "CORS" confirms the issue is likely on the local server's configuration, not just the browser policy.

[YvanMartino]

We're only seeing this issue when users are trying to navigate to the local network resource when using a url within ServiceNow itself, otherwise no problem what so ever.

I've eliminated most of the possible issues you mentioned. It seems users have only begun to experience this issue since we upgraded to Yokohama. Could there be something we need to be aware of there?