Caddy in docker blocked accessing other docker containers

[audas (sam)]

@Whitestrake

To be absolutely unambiguous here, with Matt’s example, you make a request to example.com/service-a/foo and Caddy proxies that request to 192.168.0.2:8001/service-a/foo. With YOUR config, you’re trying to make a request to 144.6.86.11/homarr/foo and have Caddy proxy to homarr:7575/foo. Did you note the missing /homarr prefix? You’ve configured Caddy to hide that part from the upstream app, so it has no idea it’s there. The app only sees Caddy asking for /foo.

Whether I am stripping it out or not is the issue I am trying to resolve.

I was not trying to make it work with handle_request - I was trying to understand what config I would need to replicate Matts example.

Its clearly obvious that it wasn’t working - I was asking how to make it work like Matts including the subfolders as Matt did.

Does that make it clear?

I was not trying to make my code work - I was wanting to know how to replicate his.

As it turned out fracislavoi answered it in another thread - I installed pihole as DNS server.

Thanks for the time.

Can't setup https with IP only and Docker

thank you, you’re a star! That was it. As I’ve spent quite a bit of time digging through docs howto set it up, reading about SNI … and when it didn’t work I’ve been pretty sure I’ve messed it up there, overlooked a typo . As for domain - I get it, it would be nice. But this is in isolated vlan, where I don’t have access to outside world. I’ll learn a bit howto set up certificate in home lab network in due time. Thx for pointing out the dangling file_server - it is remnant of the time wh…