Robert

@djsisson sure: ``` "Labels": { "caddy_0": "https://my_domain.com", "caddy_0.encode": "zstd gzip", "caddy_0.handle_path": "/*", "caddy_0.handle_path.0_redir-ghost-z8s0koow0sw0g848css8gg0k.handler": "rewrite", "caddy_0.handle_path.0_redir-ghost-z8s0koow0sw0g848css8gg0k.rewrite.regexp": "^//(.*)", "caddy_0.handle_path.0_redir-ghost-z8s0koow0sw0g848css8gg0k.rewrite.replacement": "/$1", "caddy_0.handle_path.0_reverse_proxy": "{{upstreams 2368}}", "caddy_0.header": "-Server", "caddy_0.try_files": "{path} /index.html /index.php", "caddy_ingress_network": "z8s0koow0sw0g848css8gg0k", "com.docker.compose.config-hash":...

@djsisson my domain points to IP address of my second server. But this has never been an issue as Coolify takes care of everything with Caddy. No issues with Wordpress...

@djsisson ok, thx for trying to help me. One thing I did only is I cleared it from my real domains for now. ``` 2025-01-08T16:40:24.673558565Z {"level":"info","ts":1736354424.6734734,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]} 2025-01-08T16:40:24.673723274Z {"level":"info","ts":1736354424.673663,"logger":"http.log","msg":"server running","name":"srv1","protocols":["h1","h2","h3"]}...

Trying to solve it by checking everything that I can but it seems like I lack specific details. Hope any dev will read it and try to help.

@blorente Unfortunately this doesn't work and doesn't stop issues with Caddy. There is a different underlying issue with Caddy. I went through different logs and there are problems with Caddy...

Any chance one of the devs could answer something? Maybe @andrasbacsai [apologies for tagging you] but I'm not sure if I found some bug within Coolify and how it works...

I'm stubborn and finally got a working solution, although my solution still relies on a separate Caddy proxy configuration file plus a modified docker-compose I still have a question if...