Closed Jab2870 closed 7 months ago
Hi @Jab2870 ,
No clue at all :/ I don't know the internal of Radicale auth. Best idea is to enable all possible logging Radicale side.
Hi, I got the same behaviour when trying to access the Web UI. So, you need to authenticate twice i.e. one time against the OAuth Idendity provider and another time against the Radicale web interface. However, when using the actual clients (Thunderbird, DAVx5, ...) it works. Did you already setup a user?
I do have a user set up, yes. Clients aren't working though unfortunaetly
Hi, I got the same behaviour when trying to access the Web UI. So, you need to authenticate twice i.e. one time against the OAuth Idendity provider and another time against the Radicale web interface. However, when using the actual clients (Thunderbird, DAVx5, ...) it works. Did you already setup a user?
Closing. Problem seems related to Radicale itself, than this particular image
Hi, thanks for making this. For some reason, I'm having difficulty setting up radicale to use user accounts with a reverse proxy, and wondering if you can shed some light on it.
It's set up, as per these docs: https://radicale.org/v3.html#manage-user-accounts-with-the-reverse-proxy
Here is my nginx config:
My radicale config includes:
This appears to be working as radicale docker logs show:
But I am still presented with the radicale login page. Any ideas?