I was in the midst of attempting to setup the built in apache webserver to do some light network file sharing to my iOS device that I didn't wish to sync, discovered that I can only access network related stuff from the machine itself and no other device on the network except the router can seem to discover the machine.
For example, I can access the built in webserver via it's IP and localhost (as well as *.local) if I do it directly on the same machine. If I try to access the webserver using the IP address or the .local address from my iPhone connected to the network, the page times out. I also cannot seem to ping the machine from my iPhone either, however when I ping the machine from the router, the router gets a response.
I also attempted to try installing MAMP and use the :8888 setting for Apache but it still can't be resolved from anywhere else on the network other than from the machine itself.
Curiously, I also cannot ping my iOS device from the macOS machine, only from the router. But, if I use canyouseeme.org to check if my running torrent app's forwarded port is working, the website is able to connect to the app on my machine.
The only thing to note is that both the iOS device and macOS machine are both on the latest beta versions available.
I do not feel as if this is a router issue as I've used the .local and IP address just fine to access previously configured apache setups on previous OS X versions. With most updates, it seems to reset the server configs and as such I have had to restore the settings. Up until now, this process has been working fine. I don't understand why this isn't working now, possibly a bug in the beta?
macOS Machine: 192.168.1.5