Hi, wasn't really sure how to describe this issue but.. I'm having issues with my setup and I'm not sure how to resolve it. I have NginxProxyManager setup on my unRaid server which allows me to access my Nextcloud instance over the public internet with a signed SSL certificate. It works great! As long as I'm not on my local network. As soon as I'm on my local network I cannot access it. If I attempt to ping from my local network it does resolve the correct address and respond.
I attempted to look this up and it was suggested it was a "hairpinning" issue. I also found this post from some time ago: GL-AX1800 (Flint) NAT hairpin/loopback troubles but the suggested command does not work on my router.
Easierst way would be to edit your local DNS server so it will resolve the public domain with the local IP instead of your public IP. This is called split DNS and pretty common for setups like this.
Thanks for your response! I tried this at the time but then the connection shows as insecure, meaning I'd need to install the cert on all my devices.
However.... The problem somehow resolved itself? I think it was actually an issue with Nextcloud and not the router - when I restarted the Nextcloud container it started working again. Nextcloud can be a bit weird sometimes, not sure what would have caused that specific issue.
Would have updated this thread sooner - I resolved it shortly after posting but I don't think I could edit it while pending approval.
Hmm I clearly did something wrong there then. I think I tried pointing both the domain (which goes to nginx) and nextcloud subdomain to the address (they both run on the same IP address but on different ports - router routes 80 and 443 to nginx).
Either way now it's working I don't really want to prod it at the risk of it breaking again, but will bear this in mind if it happens again and doesn't resolve with a restart.