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!

  • drdisgust@lemmy.one
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 months ago

    Hello,

    From your post and other comments it sounds like you’re under double NAT when connected to the deco access points.

    In order to solve this, go to the deco app. Go to more -> advanced -> operation mode and change it to access point mode.

    This will stop the main deco acting as a router and will hand over DNS, DHCP, routing and other such things to the main router, thus keeping your docker containers and devices connected to the deco’s on the same network

    Hope that helps!

    • 1111@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      Hello! I for sure have a double NAT problem - after writing this post I went to connect my xbox to the new mesh WiFi and it told me this was the issue, but I had no idea how to fix it until all of the great advice on here. Your instructions were spot on and now everything is working as expected! :)

      Do you have any thoughts on if I should stop the ISP router from broadcasting its 2.4 and 5GHz networks now? They seem redundant, but I saw that turning the router into modem mode will prevent me from using all it’s Ethernet ports :/