Quantcast
Channel: Support & Bugs - Matomo forums
Viewing all articles
Browse latest Browse all 5981

Upgrade to Matomo 5 brought back internal IPs

$
0
0

I’m running Matomo in Kubernetes (K3S) with the default Traefik ingress. All the visits are logged as having the container IP (10.42..). I fixed it in Matomo 4 by adding:

proxy_client_headers = “HTTP_X_FORWARDED_FOR”
proxy_ips = “192.168../16”
proxy_ips = “10...*/8”
proxy_host_headers = “HTTP_X_FORWARDED_HOST”

I also followed a post on upgrading to Matomo 5 and added:

proxy_ip_read_last_in_list = 0

But I’m still stuck with the 10.42.. IPs. Has anyone else solved this?

1 post - 1 participant

Read full topic


Viewing all articles
Browse latest Browse all 5981

Trending Articles