2026-10-11 20:20 UTC
the 192.168.65.1 address that manifested out of nowhere
Or it’s indeed the internal virtual lan your docker config uses…
Is that an actual problem or are you really just trying to fix the logs? That should be doable via headers so the real origin is preserved independent of proxying.
Replies (1)
-
@ampersandrew@lemmy.world 2026-10-11 20:23
Yeah, that appears to be the case from a link someone else linked here, but I was unable to trace that from anywhere I could find in my containers before. I am trying to fix the logs so I can see the origin of connections to my services, but I’ve been unsuccessful in getting additional configurations to resolve that.