Looking at the current instructions for installing Nextcloud (AiO) on Linux ( How to install the Nextcloud All-in-One on Linux - Nextcloud ), is it necessary to have a “public domain” and non-CGNAT setup even if it’s only for home usage (not to be accessed outside of the home network)? I can’t tell if the install is dependent on it.
A “public domain” may be also a DynDNS Domain.
With regard to CGNAT i can say a non AIO-Setup and non SNAP-Setup works also behind CGNAT with IPv6 only access from WAN. The ACME Let’s Encrypt-challenge does not need IPv4. In fact it prefers IPv6 over IPv4.
The ACME DNS challenge doesn’t require any access from the internet/WAN at all. 
3 Likes
@bb77 You are so right. I was meaning the ACME Lets’s Encrypt challenge to get and renew a certificate for https.
I’m very lazy when it comes to writing and often use copy and paste, and then I forgot to replace DNS with Let’s Encrypt.
I corrected it now. SORRY
1 Like
Well, I do have a DynDNS address, so that could work for me as well.
But I was mainly looking at the AiO option to drop into OpenMediaVault. I’m not even sure if OMV is even necessary (I just want the file shares and a file backup host), but also want to have a Jellyfin server(or rather I’m looking to eventually replace my Fedora-based Jellyfin with something not tainted by RedHat).
I ran mine purely on local IP for a long time until i added an external IP+DNS for use when i was at the office. They started blocking VPN, so i published it to the internet to get around that.
Having static IP and my own domain name, no dyndns stuff needed in my case. But i don’t see why that would not work ( as suggested above )
As mentioned by @zig , you can definitely use Nextcloud AiO within your local next work. Nothing in the install forces it otherwise. Access is an external (to Nextcloud) issue so you just access it via a local IP.