Do Traefik or Caddy handle only external proxy and routing, or localhost, too?

[theDanielJLewis]

In trying to solve #5062, I'm wondering if the problem could be Coolify's proxy.

If I have a database running on the server and access that from the server's terminal via localhost with the "external" port, is that going only through Docker, or is it going through Traefik/Caddy, too (or instead)?

[djsisson]

traefik by default is only setup to map port 80/443 to the host, so only ingress traffic on those 2 ports will go through traefik,

generally anything else will go via this path:

network interface -> OS network stack -> bridge network -> container stack -> your container (something like that) this last step would be traefik first on 80/443

[theDanielJLewis]

So accessing, for example, MongoDB running out port 27017 within the container but exposed via port 5000 would not involve Traefik? Even if accessed from my local machine instead of via localhost on the host server (but not inside the container)?

[djsisson]

traefik is only setup to handle http traffic, unless you are browsing to domains in a browser, you are not going through traefik

[djsisson]

How are you exposing your DB?

Is it in a compose using ports
Is it using the make public option
Or is it using port mappings?

If it is the middle option, then this is done using an nginx proxy which might be where your timeouts are happening, therefore switch to one of the other methods