I have just set up a brand new nextcloud server on my raspberry pi (4), running raspbian buster.
Everything seems to work locally, i can access it from multiple devices on my local network, both through the local address and the hosted address (using a NoIP domain).
From outside my network i get no connection however.
I forwarded ports 80 and 443 on my router, although it is an old arcadyan VGV7519 router and i am not entirely sure it is set up correctly.
I am a complete noob to this, which makes troubleshooting a little difficult. I hope someone can help me out.
system running nextcloud
raspberry pi 4, running raspbian.
router: Arcadyan VGV7519, forwarded port 80 and 443
Hostname: no-IP (free). - alternatives would be good to know!
Okay, but this is not a problem with your Nextcloud installation.
Looks like a DNS problem.
Just try to connect via the external IP address of your router outside your network with a smartphone, using a browser.
If this works: fine, your port forwarding works.
If not: you have a problem with your router.
When you say your “local address” I assume you mean your local IP? Not URL?
Honestly, it sounds like you’ve given NoIP your local LAN address, not your real-world address. That means, whenever you try to connect from outside your local network, NoIP is resolving to an unreachable address.
I think this is why your real-world URL works fine on your LAN. When I first set my home network up (before I started using Next/ownCloud), I also had to set up a local LAN DNS server. That way my laptop could connect easily within my LAN as well as when I was at a friend’s place on their wifi.
Without a local DNS server, trying to resolve my website’s URL from within my LAN would direct the machine to my router, not the computer on my LAN. Port forwarding only works when the port is being forwarded from the outside.
There’s an old haiku in the sysadmin world:
It’s not DNS
There’s no way it’s DNS
It was DNS
Recheck what IP address NoIP has assigned to it, make sure it’s the real-world IP an not a local LAN IP (e.g. 10.x.x.x or 192.168.x.x). That’s where I’d start.
I have checked all your suggestions. In the end, it was something else.
I have managed to solve it by replacing my ISP (and router… obviously). There were issues with portforwarding on the old, which are not present in the new. Added benefit; lower cost, better speeds, newer hardware.
Server is up and running. thank you all for your time.