Local area network permissions needed for apps using react-server in some cases?

[nickw1]

Hi @lazarv,

I'm having reports on some devices and networks that people accessing my Lilt site:

https://lilt.hikar.org/

on Chrome are reporting that lilt wishes to "look for and connect to any device on your local network".

Seems to be related to this: https://developer.chrome.com/blog/local-network-access/

This does not appear consistently: I'm finding that systems on a corporate network and Macs seem to report it most frequently.

On my device I never get this permission requested, on either Firefox or Chrome and irrespective of what network I am on.

I am wondering if this is anything to do with the internals of how react-server is working; any ideas?

Thanks.

[lazarv]

Hi @nickw1,

I checked out the Lilt site and when I select a module, the RSC request on navigation includes: :HL["https://localhost:3002/assets/layout-CiEbUtZs.css","style"]. This is the RSC request in network tab for https://lilt.hikar.org/rsc.x-component?module=DSA.

How do you host the app in production?
When using a proxy, you need to use the --trust-proxy option for the CLI start command to be able to use X-Forwarded-* headers. You can also try to specify the origin either using the --origin "lilt.hikar.org" CLI option or the ORIGIN="lilt.hikar.org" environment variable.

You need to see the public hostname or relative URL in the RSC response instead of localhost:3002 and that should resolve the Chrome LNA security issue.

[nickw1]

Hi @lazarv,

Many thanks for investigating.

The app uses an Apache reverse proxy with what I believe to be the standard configuration.

Thanks for the hints in how to configure react-server to work nicely with the proxy.