.well-known/carddav|caldav rewrite rule not recognized, http/404 instead

Nextcloud 14.0.3 (rpm version)
OpenSuse Leap 15.0
Apache 2.4.33
PHP 7.2.5

After the latest upgrade to 14.0.3, admin pages are telling me (for the first time) ‘Your web server is not properly set up to resolve “/.well-known/caldav”’. Same for …/carddav

Which in fact is true, trying for my NC instance on cloud.domain.tld to resolve cloud.domain.tld//.well-known/caldav (or carddav) leads to http/404 (not found)

**** NO idea why ****

My NC instance on my VPS (and before OwnCloud) have been running completely fine with an unchanged apache setup for years now.

NC shipped .htaccess is icluded manually in VHOST, Apache VHOST definition for NC:

<IfDefine SSL>
<IfDefine !NOSSL>

<VirtualHost *:443>

        ServerName cloud.domain.tld:443
        DocumentRoot "/srv/www/htdocs/nextcloud"
        Include /etc/apache2/conf.d/php7.conf
        Include /etc/apache2/conf.d/nextcloud.conf

        <Directory "/srv/www/htdocs/nextcloud">
                AllowOverride None
                Require all granted

        # all forbidden, no .htaccess. so include all from .htaccess:
        Include /srv/www/htdocs/nextcloud/.htaccess

        SSLEngine on

        <IfModule mod_headers.c>
              Header always set Strict-Transport-Security "max-age=15552000; preload"



Hints would be great :slight_smile:



If I change the VHOST and add the rewrite manually:

# all forbidden, no .htaccess. so include all from .htaccess:
Include /srv/www/htdocs/nextcloud/.htaccess

Redirect 301 /.well-known/carddav /remote.php/dav
Redirect 301 /.well-known/caldav /remote.php/dav

the rewrite is triggered and the error msg in the NC admin pages disappears.

But of course I would like to use the shipped .htaccess only, avoiding future upgrade errors / side effects, does anyone know why the rewrites out of the .htaccess might be ignored in my case?

1 Like