From c6ee6099b5e558ed5fda79ecb96b0dd4719aa581 Mon Sep 17 00:00:00 2001
From: Dmitry <1315874+dniku@users.noreply.github.com>
Date: Sun, 15 Mar 2026 10:56:02 +0000
Subject: [PATCH] Clarify in SSO demo that dnsmasq is required for
 Nextcloud/Authelia interaction

---
 demo/nextcloud/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/demo/nextcloud/README.md b/demo/nextcloud/README.md
index 3ca7f6e..7550bf8 100644
--- a/demo/nextcloud/README.md
+++ b/demo/nextcloud/README.md
@@ -187,8 +187,9 @@ This section corresponds to the `sso` section of the [Nextcloud
 manual](services-nextcloud.html#services-nextcloudserver-usage-oidc).
 ::::
 
-At this point, it is assumed you already deployed the `sso` demo. There is no host to add to
-`/etc/hosts` here. Instead, there is a `dnsmasq` server running in the VM and you must create a
+At this point, it is assumed you already deployed the `sso` demo. This time, we cannot simply edit local
+`/etc/hosts`, because Nextcloud SSO addon must be able to connect to Authelia by domain name
+(`auth.example.com`). Instead, there is a `dnsmasq` server running in the VM and you must create a
 SOCKS proxy to connect to it like so:
 
 ```bash