So for example, when you are off-network, your device will query from a public DNS server and receive your external IP address. What this means is that you have a DNS zone, in this example domain.name, and that you have this zone available in both public DNS and local DNS where the records differ. Replace these with yours.Īlthough I won’t go into great detail here, I also want to briefly explain the concept of split-horizon DNS since a lot of people who aren’t network admins aren’t familiar with it. In the below examples, I’ve used for Nextcloud’s FQDN, and for Collabora’s. Freshly-installed and up-to-date Ubuntu 18.04 server.Access to your local and public DNS records.Fully Qualified Domain Name (FQDN) for Nextcloud.Most of this will be outside the scope of this document. You’ll need to have some info ready that we’ll use throughout the process. I’ve installed several small Nextcloud instances using this method with good results, and I wanted to compile my setup notes in a format that’s easy to follow and reproduce. I know a lot of people are trying to get on board with Nextcloud right now during this COVID-19 pandemic with so many struggling to work from home. I will do my best to plainly emphasize things that you will need to change, but it will mainly be three things: FQDNs, IP addresses, and passwords. I will also cover how to update everything. By the end (and as of writing), this setup will have an A+ rating on Nextcloud Security Scan and Qualys SSL Server Test and a valid, self-updating certificate from Let’s Encrypt. This is a general guide to setting up a functional Nextcloud instance using Ubuntu Server 18.04.3, Docker CE, Docker-Compose, Collabora CODE, and an Apache reverse proxy.

Stop collabora code docker