tomsquest / docker-radicale

Docker image for Radicale calendar and contact server :calendar: + security :closed_lock_with_key: + addons :rocket:
GNU General Public License v3.0
562 stars 80 forks source link

Radicale won't start #118

Closed frimdo closed 2 years ago

frimdo commented 2 years ago

Hi, I am facing quite a wierd issue, where the radicale appears not to start up at all. Steps to reproduce:

$ git clone https://github.com/tomsquest/docker-radicale
$ cd docker-radicale/
$ mkdir data
$ docker-compose up
$ docker-compose logs radicale
Attaching to radicale

The Attaching to radicale is the only message that ever appears in logs. Apart from that, webpage is inaccessible although the server seems to work a bit

$ curl -f http://127.0.0.1:5232
Redirected to /.web

Tried older version (3.1.6.0) and the result is the same. I am running on Aynology DSM 6.2.4-25556 Update 4.

frimdo commented 2 years ago

Uh... Two days of debugging and now 15min after releasing I finally stumble upon the UID and GID issues. Well, I did not manage to solve this either.

tomsquest commented 2 years ago

Hi @frimdo ,

Having not output except Attaching to radicale is ok. Radicale does not log anything on start by default,

$ curl -f http://127.0.0.1:5232 Redirected to /.web

This means everything is fine, on the host you executed this.

Make sure that the port 5232 is reachable on your network (firewall, router...). I cannot help you more, this largely depends on your setup.

frimdo commented 2 years ago

Finally solved the issue by setting

    ports:
      - 5232:5232

instead of

    ports:
      - 127.0.0.1:5232:5232

in docker-compose.yml. Is there any reason for the 127.0.0.1 part?

tomsquest commented 2 years ago

Is there any reason for the 127.0.0.1 part?

Security. Only bind to the host.

Usually, you will have a proxy between you and Radicale. This proxy will do https/security... I personnally use Caddy (caddyserver). Traefyk, nginx are alternatives.