From ac54fce52243e54a1b115c2255253e7321908ebe Mon Sep 17 00:00:00 2001 From: "Simon L." Date: Sat, 25 Jan 2025 02:05:27 +0100 Subject: [PATCH] fix details Signed-off-by: Simon L. --- local-instance.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/local-instance.md b/local-instance.md index 27bc147c..9557e1c9 100644 --- a/local-instance.md +++ b/local-instance.md @@ -2,11 +2,11 @@ It is possible due to several reasons that you do not want or cannot open Nextcloud to the public internet. Perhaps you were hoping to access AIO directly from an `ip.add.r.ess` (unsupported) or without a valid domain. However, AIO requires a valid certificate to work correctly. Below is discussed how you can achieve both: Having a valid certificate for Nextcloud and only using it locally. ### Content -- [1. Tailscale network](#0-tailscale-network) -- [2. The normal way](#1-the-recommended-way) -- [3. Use the ACME DNS-challenge](#2-use-the-acme-dns-challenge) -- [4. Use Cloudflare](#3-use-cloudflare) -- [5. Buy a certificate and use that](#4-buy-a-certificate-and-use-that) +- [1. Tailscale network](#1-tailscale-network) +- [2. The normal way](#2-the-normal-way) +- [3. Use the ACME DNS-challenge](#3-use-the-acme-dns-challenge) +- [4. Use Cloudflare](#4-use-cloudflare) +- [5. Buy a certificate and use that](#5-buy-a-certificate-and-use-that) ## 1. Tailscale network This is the recommended way. For a reverse proxy example guide for Tailscale, see this guide by @flll: https://github.com/nextcloud/all-in-one/discussions/5439