I encountered a problem to connect my Iphone with nc Calendar.
The phone says “No SSL possible”. Hmm, strange. I run on my NS8 mail, NC, Collabora and nothing else. The LE certs are all obtained. The ports are forwarded to NS 8.
I followed Andys idea and use NC for adressbook, calendar and file sharing.
I can confirm that. When I use the link for iOS in the calendar settings of my NC, I also get the message regarding SSL, even though all certificates are installed correctly.
I do not have any issues connection iOS to NextCloud (AD based on NS8 VM running on Debian), neither for Calendars nor Adressbooks with iOS. (Using CrdDAV / CalDAV).
At the moment CrdDAV (for Adressbooks does have issues on some Mac versions, but on iOS NO issues!
That specific problem is dealing with the NextCloud “Files” App, nothing to do with CrdDAV or CalDAV, which uses native applications on iOS!
It’s also one of those typical users who are too lazy to implement LE and try using a self signed Cert, which won’t work two days! Not on iOS, i think not even on Android!
fwiw my cal, contacts and file app work fine on my iOS devices post migration from NS7 to NS8 with LE certs. I had to do some futzing with the files app but only because of specific, old “legacy” configs from my years old NS7, the cal and contacts just worked pre and post migration. The cal link provided by the nextcloud gui is the same as in the account settings on iOS.
I have just tried it again. I copied the iOS/macOS CalDAV address from the calendar settings of my NC instance and entered it in my iPhone. iOS complains about the LE certificate, which is considered invalid. But it is valid. The connection from the iPhone to the NC instance via the Nextcloud app from the Apple Store works without any problems.
Are you sure about the fqdn?
I would click the caldav link (copy) for iOS/macOS from the NC user’s calendar page in your desktop browser and paste that into the iOS browser, strip off everything past the fqdn and see what the iOS browser error is with the fqdn only.
It may or may not be germane to this but I get popups from iOS about a bad cert, it’s the self signed cert from the node that’s my reverse proxy, I think, problem is I can’t see the self signed cert in the node cert gui anymore, only the LE certs, irritating, and I don’t know for sure what app is triggering it and I haven’t taken the time to search it down.
If your iOS browser loads your NC login page with your fqdn both on local wifi and with wifi off through the internetz then your iOS calendar app account is probably retaining a bad cert. I would next wipe out the account and recreate it or if you have a lot of local calendar entries you don’t want to lose or something make sure the full caldav link is correct, ssl, port 443 and maybe change the password to anything hit done, let it choke and correctly reenter the password, sometimes that’ll reset the cert in the local account settings.
If your theory is correct, the NC app from the Apple Store should not work either, i think. And it does here. And there must also be a connection to the NC calendar, as I receive a reminder for each appointment stored in the NC calendar according to the setting I have made. I had initially thought that the 2FA would get in the way of a connection. But it doesn’t. If I generate a PW in the NC for access, the implementation of the NC calendar in the calendar app of my egg phone does not work either. However, I admit, however, that I don’t know enough about all the background processes of NS 9 and the NC. Therefore, there is certainly a lot of speculation on my part.
After fiddeling with the whole problem I just gave up and put the contacts in total in my phone and be done with it.
Outlook with Caldav Sync works perfect. So maybe its really something crappy with iOS.
Besides from that I get the impression that NC as a whole seems to get more buggy with every release. Especially in conjunction with the NC apps which are often don´t keep up the new releases.
So I gonna just use it for filesharing and thats it.