You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
heya I have Caddy running on Docker via Colima which acts as reverse-proxy for a variety of services (full setup here).
I noticed that I can't read original client IPs. They always read as if they’re coming from Docker itself e.g. 172.18.0.2 (when the result of docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' caddy is 172.18.0.4).
Is it because of some TCP layer proxy? Is there a way to resolve it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
heya I have Caddy running on Docker via Colima which acts as reverse-proxy for a variety of services (full setup here).
I noticed that I can't read original client IPs. They always read as if they’re coming from Docker itself e.g.
172.18.0.2(when the result ofdocker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' caddyis172.18.0.4).Is it because of some TCP layer proxy? Is there a way to resolve it?
Beta Was this translation helpful? Give feedback.
All reactions