this post was submitted on 09 Mar 2026
49 points (87.7% liked)
Selfhosted
60210 readers
944 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
Take a look at the config file (
/etc/radicale/config). It's extensively commented. Although you barely need to change any defaults for regular use.Just create an htpasswd file (with htpsswd, apache-tools or just any of the one million available online generators) and edit two lines under [auth] to read
type = htpasswdandhtpasswd_filename = <the location and file you created>.And you can start (and enable) Radicale via the systemd service usually included in the installed package. (Or for early testing just start the server manually...
radicalestarts it with the defaults from the config file. You can also configure everything with parameters but that's an insanely long list (radicale --helpif you are interested in seeing them)...)The webinterface to login will be available (by default settings) under http://localhost:5232/.
All you have to do then is change the config so Radicale listens on the server's IP instead so it's available in in your network. (Plus the usual stuff of making it available from the outside if you need that like for any other sevice)
And any calendar/contact software will bring a wizard that guides you through the process of sync'ing, usually just asking for an address to reach your server, as well as user and password.
EDIT: I looked up the defaults and you can skip all the autehntification stuff in the beginning. By default just anyone can access the webpage at port 5232. So you can just test it and only bother with authentication later (definitely when you plan to make it available from the outside, for example to sync phones).