127.0 0.0 network8/10/2023 ![]() These will be in separate config files for each site, e.g.: For example, my university assigns public IP addresses on its campus Wi-Fi network.Ĭan I also request that the backends (one for each site) also only listen on localhost? The main nginx config for the router only needs them accessible on 127.0.0.1 for the proxy_pass, so there’s no need for them to listen on all interfaces. Developer laptops typically wander across multiple networks, and it’s really easy for one to end up on some Wi-Fi network with a public IP address assigned while still running a Local site. I also cast a vote for adding this feature into Local. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed. Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |