NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dtskip
May 15, 2021Guide
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...
CrimpOn
May 15, 2021Guru - Experienced User
Have you tried connecting using the Orbi public IP address, rather than the Domain Name?
- dtskipMay 15, 2021Guide
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.
- CrimpOnMay 15, 2021Guru - Experienced User
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.)
- dtskipMay 15, 2021Guide
CrimpOn wrote: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.)
I didn't bother providing the extra information because I was hoping someone might be able to pinpoint a known issue in the latest firmware update. Looks like that window is shut.
Basically I have an Unraid Server connected to my Orbi Router via Ethernet. On this server I run several containers, including about 4-5 configured with a Reverse Proxy (LetsEncrypt/Nginx) and my custom domain (for example, mydomain.org). With Nextcloud, I have it configured as a subdomain (nextcloud.mydomain.org).
Of course, all of these docker containers have a local gateway, which comes in the form of my server's local IP+port, but I prefer accessing Nextcloud through my custom domain for a variety of reasons. For some reason however, upgrading to the latest Orbi firmware appears to have the effect of blocking my custom domain, even though my internet still works perfectly well, and I can access my custom domain from outside my network, and through a VPN.
As if things couldn't get anymore confusing: after running some more tests, I can now conclude this problem only occurs with devices connected to the Orbi via ethernet cable. In other words, the PC I'm typing this from cannot connect to the custom domains, but my phone and laptop connected to the Orbi via Wi-Fi can. If I connect my Laptop via Ethernet to the Orbi, it no longer works. I am honestly baffled.