NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

dtskip's avatar
dtskip
Guide
May 15, 2021

Cannot access self-hosted domains after updating to V2.7.2.104

I self-host a Nextcloud server among other things on a domain I purchased. But since updating my Orbi from V2.5.1.16 to V2.7.2.104, those domains simply do not load anymore, unless I connect to a VPN. They work fine from outside the network, but not from within my own network. What gives?

 

I can only conclude this is a problem from the Orbi, but have no idea where I should be looking.

8 Replies

Sort By
    • dtskip's avatar
      dtskip
      Guide
      May 15, 2021
      FURRYe38 wrote:

      Revert back to v16? 

      Not an option. I had enough trouble with the last nightmare of downgrading firmware. It just goes into an endless loop of "Please wait" when trying to downgrade the router.

  • CrimpOn's avatar
    CrimpOn
    Guru
    May 15, 2021

    Have you tried connecting using the Orbi public IP address, rather than the Domain Name?

    • dtskip's avatar
      dtskip
      Guide
      May 15, 2021
      CrimpOn wrote:

      Have you tried connecting using the Orbi public IP address, rather than the Domain Name?

      Yes, and it works with some of my docker containers, but not Nextcloud, which always redirects to the domain. That's how I prefer it too, so I only have to connect to a single domain whether I'm connected to my home network or not.

       

      I want to find the problem this firmware update caused which seems to be blocking my personal domain.

      • CrimpOn's avatar
        CrimpOn
        Guru
        May 15, 2021

        I am struggling to come up with an experiment to reproduce the issue.  Probably because of not understanding how NextCloud and "domains" work.  (one sentence said "domain I purchased" and another said "those domains".  Are there more than one domain?

         

         I found this guide on running NextCloud:

        https://docs.nextcloudpi.com/en/how-to-access-from-outside-your-network/ 

         

        Is this even close to what is going on:

        • There is a Linux server on the local network running NextCloud, which listens for connections on ports 80 and 443.
        • On the Orbi router, ports 80 and 443 are forwarded to the server
        • At either My-IP.com or Dyn.com a domain name is associated with the public IP of the Orbi.
          (I sense a potential issue here because Orbi's DDNS works with either My-IP.com or Dyn.com and NextCloud talks about using either My-IP.com or FREEDNS.  Which are you using?)

        I seem to recall there being issues with forwarding port 443 through the Orbi.  (Probably not remembering correctly.)