Cleb

Members
  • Posts

    1
  • Joined

  • Last visited

Everything posted by Cleb

  1. I've just finished setting up nextcloud as per the latest tutorial from Spaceinvador One, and I have everything working, except that my router does not support NAT loopback. This means I cannot access nextcloud via the domain name I set up from within my local network, but can still use the local ip address along with port 444. This obviously creates problems with devices that move in and out of my local network as I cannot have both addresses setup on them (as far as I know). Does anyone here know of a workaround for no NAT loopback? (Other than buying a new router as this isn't an option right now) From my research on it people have been able to get around this issue by running a local DNS which resolves the domain name used for external access into a local IP address, so the router never has to deal with it. I installed pihole to see if I could do this, but DNS doesn't resolve an IP address with a port number, just an IP. So this would only get me as far as having my domain name point to my server IP, but not to the nextcloud docker on port 444. I saw one or two people on other forums mention SRV records as a way to include ports, but information on that starts getting very technical and quickly goes over my head. Any help/suggestions would be great!