"Account name / password could not be verified."
We show you the solution to the known problem with CalDAV and MacOS.
Granted, this article has nothing to do with our regular articles. Nevertheless, we did not want to deny the solution to the above problem with MacOS High Sierra (10.13.6) and MacOS Mojave (10.14.) To anyone.
We also use the CalDav system. Now, however, it was time to take the dusty macOS server to the next level. Accordingly, we installed OwnCloud on a Synologybox. At first the system worked perfectly. After a short time (and the integration of further Macs), however, disillusionment spread. Many of our Macs in the office encountered the error “Account name / password could not be verified”. After viewing countless forum posts and trying various ways to fix the problem, frustration spread.
To the solution:
The problem seems to lie in the fact that Apple MacOS X does not get the assignment of the /.well-known parameter correctly. Accordingly, we have (at first) extended the .htaccess file with an addition.
1. Change htaccess file
Redirect 301 /.well-known/carddav /owncloud/remote.php/dav Redirect 301 /.well-known/caldav /owncloud/remote.php/dav
These additions must be in the .htaccess file.
2. Customize certificates
The adaptation of .htaccess then led to success (at least) on some computers. However, especially under Mojave, this did not lead to the final solution. After we couldn't downgrade our computers either, there was no choice but to look further. Then we scoured the endless log files of our OwnCloud server. The next problem came up: the other Macs simply didn't trust our Synology server. So the solution was very simple. The server's certificate was simply exported on a computer on which the aforementioned modification of the .htaccess file had already been successful, and imported on the computer on which it did not work. After the corresponding trust settings were set here, as can be seen in the screenshot below, the exchange worked without any problems.
It is therefore important that first the .htaccess and then the certificates (just go through keychain management and search for Synology or similar) are adjusted.
We hope that we have also been able to help you solve this problem and are looking forward to saving you a few nerves. We are also pleased if you leave a comment on the subject and tell us your own testimonials.
3. Check the blacklist
If the problem persists, you should take a closer look at your Synology's blacklist. You can find this in the Synology menu under "Control Panel" -> "Security" -> "Protection" -> "Allowed / Blocked List". It is possible that your IP address is in the block list. You then simply have to remove these.
Super thank you!! Has advanced me after hours of search!