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!
Can you give us some more details about how your network, mesh and machines are setup?
Are you trying to access the containers from the machine they’re running on, or from a different machine?
Is the container host moving between different AP’s, or is it on ethernet?
What IP address do you get when connected to the different access points? Does it change?
Are your access points in Access Point only mode, or are they acting as routers? What brand/model?
How are the mesh access points connected - powerline, ethernet, wifi meshing?
Sure thing! I’ll answer everything as best I can.
The machine is a single laptop running Mint. All the docker containers are being served from this machine, and during this testing I was trying to access them all from that same machine. I observed the containers were up and running properly with docker stats cmd and I saw they were accessible over the original IP when using the ISP WiFi.
The access points are TP Link Deco, it’s 3 units, the first of which is connected via ethernet to my ISP provided router (Virgin Media Superhub). I believe they are WiFi meshing. I can’t tell too much more about how they work ‘under the hood’ as the setup was very… ‘consumer friendly’ and didn’t cover much technical detail
When I connect to this network and run ifconfig it looks like the IP changes in the last few digits. I thought if I used that IP with appropriate ports I might be able to view my servers, but that was not the case.