this post was submitted on 14 Sep 2025
80 points (98.8% liked)
Selfhosted
60281 readers
645 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When I installed radicale last, i had problems with auth and exposing it. I think either I misunderstood something or it was left as an exercise for the reader. Anyways...
I'm a noob and I managed to set it up following mostly these instructions that make user of this docker compose file. I remember I had to do something slightly different, but I managed to figure it out relatively easily. You could have a look at it and see if it helps.
The documentation says what settings you need to enable for it to work. It also says that it takes the remote user in the X-Remote-User header. I use Authelia and it puts the remote user in the Remote-User instead, so i added a middleware to traefik that renames the header to the one expected by radicale. The only problem remaining is that radicale presents the auth page anyway, and you have to login with the same username as the auth header but with any password