Closed cyberius0 closed 1 year ago
@cyberius0 you found the issue eventually?
@cyberius0 you found the issue eventually?
Within
location /radicale/ {
[...]
we need a trailing slash at the end of the destination.
e.g. proxy_pass http://localhost:5232/;
or proxy_pass http://<docker-container ip>:5232/;
This is working fine if we enter the IP of the radicale docker-container..
BUT: As the IP of the docker-container ist not static and can change, normally we do it like this:
set $upstream http://radicale:5232;
proxy_pass $upstream/;
Now nginx gets the ip by resolving the hostname.
BUT: This only works without a trailing slash. (Why ?)
To make it work with the trailing slash, we have to do use the little "hack" above.
:+1: for the info @cyberius0
I am glad to use Caddy as the reverse proxy :) much simpler :)
solved (see Edit)
hey there, sorry to bother, but could you share your Caddyfile-Config?
i can't seem to get mine to work.
i have a simple
radicale.domain.tld {
reverse_proxy radicale:5232
}
I tried setting the Port to just
5232:5232
instead of
127.0.0.1:5232:5232
and proxy to
ipOfServer:5232
and i tried adding a
header_up X-Script-Name /radicale
from the Docs of the Upstream Project, but none of that worked.
Edit: NVM, i'm stupid, it was a networking Issue. I forgot to add Radicale to my Proxy Network. i'm an Idiot
@Neon-44 FYI I added my Caddyfile to the Readme https://github.com/tomsquest/docker-radicale/?tab=readme-ov-file#running-behind-caddy
edit: solved the problem by myself.
In case anybody wants to use nginx reverse-proxy with this container and is getting an error like
The requested resource could not be found.
orThis is my working config file for nginx: