Chrome will allow it. Links will also work from any site. https://developer.chrome.com/blog/private-network-access-update/ https://developer.chrome.com/blog/pr

Chrome will allow it. Links will also work from any site. https://developer.chrome.com/blog/private-network-access-update/ https://developer.chrome.com/blog/private-network-access-upd... I believe the change is that http:// http:// pages on public websites won't be able to talk (such as via XHR/fetch, embedded images/scripts/css) to private IP address or sites with domains that resolve to private IP addresses. One obvious workaround is to change the requesting page to https:// https:// instead of http:// http:// . This is somewhat difficult because then there's the problem of mixed content, since it's often difficult to get an https:// https:// certificate for the server that runs on the private IP address. There are 2 other workarounds listed on the Chrome blog post: WebTransport and and Reverse embedding (which means running the site on a private IP address instead of a public IP address). It looks to me like those could work in the Portal case. Full disclosure I work at Google, but not on Chrome.