centersl/nextcloud-docs
1
0
Fork 0
mirror of https://github.com/nextcloud/documentation.git synced 2026-03-27 13:38:39 +07:00
Code Issues Packages Projects Releases Wiki Activity

fixup

Browse Source 
Co-authored-by: MichaIng <micha@dietpi.com>
Signed-off-by: Jakub Jelen <jakuje@gmail.com>
This commit is contained in:
Jakub Jelen
2023-06-15 22:57:41 +02:00
committed by GitHub
parent cbe2b80dc8
commit f1976af78c
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
admin_manual/issues/general_troubleshooting.rst
View File

@@ -268,15 +268,14 @@ document root of your Web server and add the following lines::
Make sure to change /nextcloud to the actual subfolder your Nextcloud instance is running in.
.. note:: Note, that if you are putting the above configureation directly to
the apache configuration (generaly in ``/etc/apache2/sites-enabled/``),
you will need to prepend the first argument of each of the above
``RewriteRule`` option with a forward slash ``/``, for example
.. 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
each ``RewriteRule`` option with a forward slash ``/``, for example
``^/\.well-known/carddav``.
This is because Apache already normalizes the values for the use in
``.htaccess`` by dropping any number of leading slashes, but it does
not for the use in its main site configuration where the forward slash
is still present.
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.
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.