There are some warnings regarding your setup.
* Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the [documentation](https://docs.nextcloud.com/server/14/go.php?to=admin-setup-well-known-URL).
* Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the [documentation](https://docs.nextcloud.com/server/14/go.php?to=admin-setup-well-known-URL).
i tried add the lines bellow to my .htaccess and i have commented the ones above and my nextcloud isn’t working anymore:
Using redirect rules from mod_alias, as in OT, to let the clients send a new requests to the redirects address/path.
Using rewrite rules from mod_rewrite, handling the path adjustment silently server side without new client requests, as suggested in the follow up answers.
I don’t know much about pros/cons, the first solution seems a bid simpler though.
But each of them need to be set inside your webserver or vhost config, as long add Nextcloud is not already your webroot. How should otherwise the server know about requests/redirects if the related rules ate in a sub directory .htaccess where it’s not yet inside .
For the same reason the default .htaccess inside Nextcloud directory does not have any effect. It just works with Nextcloud add webroot, pointing to the then correct relative path without /nextcloud subdir inside.
below the <VirtualHost>...</VirtualHost> section (but above</IfModule>).
Although this works and I don’t get the warnings anymore, I don’t understand at all why it works. I would appreciate any hints why the lines work in this place and not in the nextcloud.conf or any .htaccess file in /var/www/html or /var/www/nextcloud like the documentation suggests…
I don’t have a httpd folder in my etc folder like mable but I’m also not running apache. I am running nginx. I tried checking out the ssl.conf for my nginx settings but when I add the extra lines it makes it so that my nginx won’t start or restart.
I tried adding it to etc/nginx/sites-enabled/cloud.jackalope.tech (that’s the name of my cloud server) and restarted but I’m still getting the same caldav related error codes in the web portal
I fixed this issue and now I’m getting it again when trying to update to NC 17… very annoying this keeps popping up. I have no clue why it’s happening. I’m nearing the point where I think I might just try wiping this server and starting over. Doing so would be very annoying though and I’m not looking forward to the prospect.
This seems to be a very annoying and unresolved “issue” for a long time.
The issue is not in any of your config files at all, it is in the apache configuration.
In the section defining the directory where your nextcloud installation resides, please make sure that the following options match:
Require all granted
Options FollowSymLinks MultiViews
If AllowOverride is not set this way, it prevents other configuration files from overriding the options as set by apache, which would prevent .htaccess from working as expected.
This could either be in the httpd.conf file, or a virtual host file, depending on your setup.
This is what it would look like in the httpd.conf file, in the DocumentRoot - your configuration may vary.
here is the open issue on github:
would you please tell us what changes have you made and to what files?. i dont have httpd.conf file. all i have are those directories 1. sites-avaliable in which the following files reside 000-default.conf default-ssl.conf and the sites-enabled directory in which there is only the 000-default.conf file, and lastly the apache2.conf file i added those two lines: