nextcloud certificate keeps not being accepted #1289
-
Hi everybody,
I am trying to connect a local Nextcloud account; however, the app keeps prompting information about an unknown certificate. Then when I accept the certificate, it jumps back to the field where you enter the nextcloud URL. I have tried using caldav manually (instead of going through the nextcloud app, which, by the way, has connected to the server fine after accepting the certificate), but it produces the same result. If I go through the steps again (enter URL again, accept certificate again) after having done so once before, the app will crash (Android will prompt to close the app or to wait). Another account is connected on another phone in the same wifi network. It is a Google Pixel 6, also running GrapheneOS and Android 15. So this error doesn't seem to have anything to do with neither Nextcloud, nor the OS (Graphene), nor DavX5 itself. But then, why does it happen on this one phone (Pixel 7)? Then back to this Try again, then this It does not make a difference whether or not I trust system certificates or not. DAVx5 has all rights / permissions that I can give it The phone was previously connected to a different local nextcloud instance (both via nextcloud and DAVx5). That worked fine. Since it was also local, it also had a manual certificate. We deleted all cache and app data from both nextcloud and DAVx5, then we completely deleted, then re-installed both apps. This error still occurs. This is kinda weird. Connect the nextcloud app would always work fine, even with this certificate. But DAVx5 will not connect, not even manually (using the dav URL instead of choosing "Nextcloud" as provider). It will try to connect, show the "accept certificate" thingy again (so it does connect to the server), but then it stops just as described above when trying to connect via Nextcloud. Can you please help me fix this? If you need any further information, please just tell me what to find and I'll try and add it. Thank you in advance for your help :) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It's this problem: #1288 Will be fixed in 4.4.7, which will be released very soon. Since you have Google Play, you can also enter the beta channel and get the fix immediately with 4.4.7-rc.1 (which is already in public beta). |
Beta Was this translation helpful? Give feedback.
-
Ups, sorry I did not find that issue. But yeah, that is exactly it. Thank you :) |
Beta Was this translation helpful? Give feedback.
It's this problem: #1288
Will be fixed in 4.4.7, which will be released very soon. Since you have Google Play, you can also enter the beta channel and get the fix immediately with 4.4.7-rc.1 (which is already in public beta).