Caddy in docker blocked accessing other docker containers

[audas (sam)]

Really not sure why we are being told we can not use paths from an external IP to be proxied when this is exactly what it is meant to do?

There is even a WIKI how to do exactly what I am asking from one of the authors of Caddy Matt Holt describing precisely what I am attempting to do.

Using Caddy as a reverse proxy in a home network

If you want to run a service inside a Local Area Network (LAN) such as your home or office – and especially if you want to be able to access it from outside that network – Caddy can help you accomplish this quite easily. This guide will show you how. It assumes you’ve never done this before, but that you have some technical proficiency and are somewhat knowledgable about your own network. Do this at your own risk. There are several ways to make private services accessible from other n…

I can’t really understand why this is no longer meant to be done as it “subfolders” and will break the paths - yet this wiki describes exactly that.

Just trying to wrap my head around why we are meant to use sub domains now and not paths - and why paths wont work etc

How has this changed ?

Is there an alternative system that I could approach this with?

Thanks in advance.