I can’t confirm that: I just added a CalDAV account to my iOS12 phone from my testinstallation with self signed certificate without any problems (without installation profile) - so selfsigned certificates do work with iOS 12 (of course you have to tell iOS12 to trust the certificate when adding the CalDAV account).
@regatta: could you add a selfsigned certificate and try whether that solves the issue for you?
Thank you Bernie, solved! But it wasn’t the port number. When setting up the calDav-account it is cruical to write the server address the very first time correct. And dont write “https://” when typing the server address.
To me it looks like Apple has dropped support for synching CalDAV without SSL with iOS12. So, what in your case probably might help, is configuring your webserver to serve Nextcloud via https and then delete/add your account in iOS again.
I will happily do that when the problem is solved. Currently, there is a workaround for the problem which is a completely different thing. Marking the thread solved would lower the chances to get the bug in either iOS12 or nextcloud fixed.
Same problem here: we’ve got four iphones 6 & 7. One have updated to ios 12, and then had no more reacted to authentication “status 401” from nextcloud.
Other iphones (until "iOS/11.4.1 (15G77) dataaccessd/1.0"… ) and thunderbird/Lightning (on windows) are still working well; the fault seems to come from ios service “iOS/12.0 (16A366) dataaccessd/1.0”.
FreeBSD 11 + nginx 14 + php7.1 + postgresql 9.6 + nextcloud 14 (all upgraded and uptodate as yesterday).
nextcloud: http (not ssl) in lan only.
It looks like Apple dropped cal-/carddav sync support for plain http.
So you have to configure your server to serve Nextcloud via https and not via http to make the synchronization work again with your iOS12 devices (you might then have to delete the accounts from the devices and readd them).
A selfsigned certificate is good enough.