I just installed a mesh WiFi network in addition to my ISP-provided router that could barely reach upstairs. I had some locally hosted services set up as per Mediabox. All containers were set up with my machine IP(?) 192.xxx.x.xx and were working great inside my network, which is all I wanted to do while I’m learning. I noticed today that if I connect via the other, mesh WiFi network that this IP can’t be accessed, despite it being the same machine. What’s going on?
All advice much appreciated as I am (obviously) a self hosting novice!
Sweet! Yeah, I’m guessing that the iptables-mangle and landing page link setup relies on getting that IP before populating the page, and that it’s not reactive to changing IP address. It might have worked if you were disconnecting networking all together, and joining a different network, but with the wonky way wifi roaming actually works, the mediabox management scripts probably never noticed there was a need to re-trigger.
You’re looking for mdns! Depends on which distro you’re on. For apt based stuff like mint, look for mdns (used to be libnss-mdns on raspberry pies, guessing it’s the same for lint? It’ll install avahi zeroconf stuff if it’s not there already. Check the service is running, then ping $HOSTNAME.local - replace with whatever your host name is.