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.
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 just trying to fix the logs. That should be doable via headers so the real origin is preserved.
the 192.168.65.1 address that manifested out of nowhere
Or it’s the internal virtual lan your docker config uses…