Well-known carddav and caldav - Apache 24 Redirect and Authorization: Basic setup

[Nextcloud version (eg, 12.0.2): 15.0.4
Operating system and version (eg, Ubuntu 17.04): Official Docker running Synology DSM Linux
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.x
PHP version (eg, 7.1): 7.2

The issue you are facing: I’m using the included .htaccess file and not sure what I’m doing wrong. I’m facing a couple issues:

  1. Well-known. The redirect engine is on and the redirects work, but for some reason Nextcloud gives an error that the server isn’t configured for .well-known. In a browser it behaves as expected, but in most apps I can’t just enter the server address, I have to enter the /remote.php path. This has been happening since installation and I am not great with Apache redirects so help would be much appreciated.
  • Your web server is not properly set up to resolve “/.well-known/caldav”. Further information can be found in the documentation.

  • Your web server is not properly set up to resolve “/.well-known/carddav”. Further information can be found in the documentation.

  1. WebDav. I had some issues upgrading from 15.0.2 to 15.0.4. I got everything restored in the end but one thing doesn’t work which is syncing bookmarks. I get the following error in the log when Floccus tries to connect. Floccus settings haven’t changed so I’m assuming it’s a config error in the server.

Sabre\DAV\Exception\NotAuthenticated: No public access to this resource., No ‘Authorization: Basic’ header found. Either the client didn’t send one, or the server is misconfigured, No ‘Authorization: Bearer’ header found. Either the client didn’t send one, or the server is mis-configured, No ‘Authorization: Basic’ header found. Either the client didn’t send one, or the server is misconfigured

Is this the first time you’ve seen this error? (Y/N): 1. N and 2. Y

Steps to replicate it:

Described above

The output of your Nextcloud log in Admin > Logging:

Happy to send the log, but can you tell me what to look for to sanitize it? It’s quite long and I want to avoid any links to my server or other sensitive info posted

LOG 

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'htaccess.RewriteBase' => '/',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' => 
  array (
    0 => 
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 => 
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
    ),
  ),
  'instanceid' => 'xxx',
  'passwordsalt' => 'xxx',
  'secret' => 'xxx',
  'trusted_domains' => 
  array (
    0 => 'domain.net',
    1 => '192.168.x.x',
  ),
  'datadirectory' => '/var/www/html/data',
  'dbtype' => 'mysql',
  'version' => '15.0.4.0',
  'overwrite.cli.url' => 'https://domain.net',
  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => '172.17.x.x:3307',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'oc_admin',
  'dbpassword' => 'xxxx',
  'installed' => true,
  'twofactor_enforced' => 'false',
  'twofactor_enforced_groups' => 
  array (
  ),
  'twofactor_enforced_excluded_groups' => 
  array (
  ),
  'mail_smtpmode' => 'smtp',
  'mail_smtpsecure' => 'ssl',
  'mail_sendmailmode' => 'smtp',
  'mail_from_address' => 'xxx',
  'mail_domain' => 'domain.net',
  'mail_smtpauth' => 1,
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtphost' => 'mail.domain.net',
  'mail_smtpport' => '465',
  'mail_smtpname' => 'xxx',
  'mail_smtppassword' => 'xxxx',
  'maintenance' => false,
  'integrity.check.disabled' => true,
  'updater.secret' => 'xxx',
  'loglevel' => 0,
  'theme' => '',
);

The output of your Apache/nginx/system log in /var/log/____:
The following error just repeats a couple times in apache24-error-log. Nothing else recent. Or did I grab the wrong one?


2019-02-24T00:17:58+07:00 NAS AH00558: httpd24: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message
2019-02-24T00:17:58+07:00 NAS [Sun Feb 24 00:17:58.666124 2019] [mpm_worker:notice] [pid 24164:tid 139840623015808] AH00292: Apache/2.4.29 (Unix) configured -- resuming normal operations
2019-02-24T00:17:58+07:00 NAS [Sun Feb 24 00:17:58.666132 2019] [core:notice] [pid 24164:tid 139840623015808] AH00094: Command line: '/var/packages/Apache2.4/target/usr/local/bin/httpd24'
2019-02-24T15:10:37+07:00 NAS [Sun Feb 24 15:10:37.309672 2019] [mpm_worker:notice] [pid 20698:tid 139825894053760] AH00292: Apache/2.4.29 (Unix) configured -- resuming normal operations
2019-02-24T15:10:37+07:00 NAS [Sun Feb 24 15:10:37.309764 2019] [core:notice] [pid 20698:tid 139825894053760] AH00094: Command line: '/var/packages/Apache2.4/target/usr/local/bin/httpd24'
2019-02-24T15:10:39+07:00 NAS [Sun Feb 24 15:10:39.684026 2019] [mpm_worker:notice] [pid 20698:tid 139825894053760] AH00297: SIGUSR1 received.  Doing graceful restart

I think this kind of problem has already been reported several times in the past. By
searching the help forum I found e.g. this request, which most likely should help you too.

Thanks for replying. Maybe I’m still not quite getting it with nextcloud versions. It seems 13,14, and 15 are all updated? Maybe that’s why I ignored the thread you referred to as it was talking about version 13.

Anyway, it still wasn’t that helpful. Seeing as I’m running a docker container which has been downloaded so many times, I would assume if I’m running the right version of apache, the .htaccess should work as is. There were some solutions in that thread, but nothing about the cause of the problem, which is what I’m interested in. Why would the redirects work in a browser but show as an error in the admin panel?