I recently configured a mini server using Proxmox and Docker. Now I’m trying to set up Nextcloud without the use of a domain (I was able to get it started with a domain, but this time I’d like to get it running with IP only), but I can’t seem to find any useful documentation to get started and figure out how to do it.
I currently use Pi-hole as my DNS server, and many people have told me that I could make the www.mydomain.com address point directly to my IPV4.
Does anyone know of any video tutorials or resources that can help me? In a nutshell I would like to configure nextcloud with https but without exposing anything.
Hey, just to clarify your question, are you interested in only using Nextcloud while you’re on your LAN? Or do you want to be able to access it remotely, but without having any ports open on your router?
In the first case, you could just access it via the IP address (assuming this works with proxmox) – you wouldn’t have to set up any DNS entries, and this would be the most simple solution.
If you do want to type in www.mydomain.com and have it redirect to your nextcloud instance, you can do this with pihole. Go to the admin interface, go to local dns, and add an entry for “www.mydomain.com” that points to your nextcloud IP address. Now any machine using the pihole for DNS will be directed to your nextcloud machine.
The pitfall to this approach is that if one of your machines uses another DNS, perhaps as a fallback, it may contact “www.mydomain.com” on the internet, which could be harmless or could lead to problems. So the best practice is to own the registration for “www.mydomain.com”, or you can try using a domain space that has historically been used for private use only, and you’ll probably be fine. Here is the rabbit hole: dns - How to choose a sensible local domain name for a home network? - Super User TL;DR, you’ll probably be fine using a .home domain, and even better off with .home.arpa
One wrinkle is accessing nextcloud with HTTPS and getting the certs to work. Since you’re local only, there should be nothing that risky about accepting a self-signed certificate, as long as you are reasonably sure no one will break into your LAN.