mirrors/nextcloud-documentation
3
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2025-10-26 11:18:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update general_troubleshooting.rst

Browse Source 
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 <zenlord@users.noreply.github.com>
This commit is contained in:
Vincent 2024-09-24 13:05:56 +02:00 committed by GitHub
parent 975247c3c5
commit 35bca1f868
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
admin_manual/issues/general_troubleshooting.rst
View File

@ -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.