From 35bca1f868744a99b6d7e48e83e486b739c080c5 Mon Sep 17 00:00:00 2001 From: Vincent Date: Tue, 24 Sep 2024 13:05:56 +0200 Subject: [PATCH] Update general_troubleshooting.rst Correcting the information in the *note* in section "Service Discovery" - it appears to not be true in all circumstances, so I added a nuance and a reference to a scenario in which it is not true Signed-off-by: Vincent --- admin_manual/issues/general_troubleshooting.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/admin_manual/issues/general_troubleshooting.rst b/admin_manual/issues/general_troubleshooting.rst index 178c41f6818..aa5adf9d331 100644 --- a/admin_manual/issues/general_troubleshooting.rst +++ b/admin_manual/issues/general_troubleshooting.rst @@ -287,12 +287,12 @@ Make sure to change /nextcloud to the actual subfolder your Nextcloud instance i .. note:: If you put the above directives directly into an Apache configuration file (usually within ``/etc/apache2/``) - instead of ``.htaccess``, you need to prepend the first argument of + instead of ``.htaccess``, you may need to prepend the first argument of each ``RewriteRule`` option with a forward slash ``/``, for example ``^/\.well-known/carddav``. This is because Apache normalizes paths for the use in ``.htaccess`` files by dropping any number of leading slashes, but it does not - do so for the use in its main configuration files. + always do so for the use in its main configuration files (depending on your operating system: Debian Bullseye does not need these leading slashes). If you are running NGINX, make sure ``location = /.well-known/carddav {`` and ``location = /.well-known/caldav {`` are properly configured as described in :doc:`../installation/nginx`, adapt to use a subfolder if necessary.