search

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

"Address not available" when starting docker #67

Closed northorsouth closed 4 years ago

northorsouth commented 4 years ago

Hello, I'm having an issue starting this docker container on my unraid server. I'm using the "production" config with all the extra parameters provided. It starts successfully when I don't include the "hosts" field in the config, but I can't access the webUI. If I add in my server URL in the hosts field, I see an error saying "address not available". I have port 5232 exposed.

tomsquest commented 4 years ago

Hi,

The host field is somewhat internal to the container, and shouud stay as 0.0.0.0. It tells Radicale to accept connection from anywhere. Docker will send connection to the container with an address that is not 127.0.0.1, so it is easier to not restrict the access that way. And it should not be your server URL, which the container does not know anything.

The issue maybe the frontend (nginx, apache, caddy, traefik) that unraid setup on top of it. And for that case, I can't help.

northorsouth commented 4 years ago

I still can't access the webui, even if I go directly to lan-ip:5232. So i don't think its the proxy. But 0.0.0.0 is the default right? So I should just leave the hosts line out of the config?

-------- Original Message -------- On Feb 12, 2020, 7:20 AM, Thomas Queste wrote:

Hi,

The host field is somewhat internal to the container, and shouud stay as 0.0.0.0. It tells Radicale to accept connection from anywhere. Docker will send connection to the container with an address that is not 127.0.0.1, so it is easier to not restrict the access that way. And it should not be your server URL, which the container does not know anything.

The issue maybe the frontend (nginx, apache, caddy, traefik) that unraid setup on top of it. And for that case, I can't help.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

tomsquest commented 4 years ago

No, the default is 127.0.0.1 for security purpose (when Radicale runs on the host)

northorsouth commented 4 years ago

Ah, that was my issue. Working now with 0.0.0.0:5232, also proxied to port 80. Thanks for the help!

-------- Original Message -------- On Feb 12, 2020, 8:42 AM, Thomas Queste wrote:

No, the default is 127.0.0.1 for security purpose (when Radicale runs on the host)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

shasycouk commented 3 years ago

Ah, that was my issue. Working now with 0.0.0.0:5232, also proxied to port 80. Thanks for the help! …

Hi there, sorry for having to write in this issue, but I wasn't able to find many people that are running this on unRAID. I can get the docker to work in its standard configuration but I'm having problems with properly setting it up anything beyond that. Would you mind sharing your unRAID radicale docker configuration (in advanced view)? @northorsouth Alternatively, If you would rather not share it here, I'd appreciate an email (shasycouk@pm.me) or a dm on twitter (benediktLEB). Thanks ahead.