Unknown Error after successful auth in local Nextcloud installation (https/ ACME cert)

[L00PN00B]

Describe the bug
Adding an Nexcloud account via Nextcloud method failed on planity client side with the error 'To many redirects'. Nextcloud Login in Browser and granting access for planity worked without any error on the server side.

To Reproduce
Steps to reproduce the behavior:

1. Go to planity
2. Click on 'Settings'
3. Scroll down to 'Online accounts'
4. Add '+' account choose Nextcloud
5. add Nexcloud domain: https://nc.bastion.kirsch.kiwi:1234
6. Browser open, Nextcloud login page, login and grant access for planity
7. confirmation window in browser shows that I can close the browser, all should be fine
8. planity cause the following error:
   .
   Expected behavior
   A clear and concise description of what you expected to happen.

Screenshots

-> To many redirects. Nextcloud is running in a container with local ACME wildcard certificate and port.

Desktop (please complete the following information):

• OS: OS: CachyOS x86_64
• DE: Budgie 10.10.1
• WM: labwc 0.9.3 (Wayland)
• Kernel: Linux 6.19.2-2-cachyos
• Version: planify 4.18.0-1

Additional context
The native Nextcloud Linux app is working with the same auth method without an issue. So it should theoretically work. :) Will try the caldav method later.

[byquanton]

What happens if you try running?
curl -L https://nc.bastion.kirsch.kiwi:1234/.well-known/caldav
It should show this error:

<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception>
  <s:message>No public access to this resource., AppAPIAuth has not passed, This request is not for a federated calendar, 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</s:message>
</d:error>