Umami Shows Wrong Country or "Unknown" Location

How to fix it

Try these in order — the most common fix is first.

1. 1. Enable Cloudflare location headers

   Copy steps
   1. In Cloudflare, open your site > Rules > Settings > Managed Transforms
   2. Turn on Add visitor location headers
   3. In Nginx, add proxy_set_header for CF-IPCountry, CF-Region-Code and CF-IPCity using $http_cf_ipcountry etc.
   4. Restrict your origin so only Cloudflare can reach it
   Did this fix it? Yes No

2. 2. Forward the real visitor IP

   Copy steps
   1. Make your proxy pass X-Forwarded-For / X-Real-IP
   2. If you use a custom header, set CLIENT_IP_HEADER to it
   3. Set TRUSTED_PROXIES to your proxy IP ranges (or presets like private)
   4. On cloud load balancers that drop the IP, enable proxy protocol
   Did this fix it? Yes No

3. 3. Use the built-in geo database

   Copy steps
   1. If you only get country headers, set SKIP_LOCATION_HEADERS=1
   2. Optionally set GEO_DATABASE_URL to a MaxMind-compatible MMDB file
   3. Restart Umami
   Did this fix it? Yes No

Symptoms

All visitors appear from one country (often the server's), countries show as Unknown, or city and region are missing or garbled.

Why it happens

• Reverse proxy or load balancer not forwarding the client IP
• Cloudflare sending only CF-IPCountry by default
• Multiple proxies in a chain without TRUSTED_PROXIES set
• A non-standard IP header not configured

This guide also covers

• umami country unknown
• umami wrong location
• umami cloudflare location
• umami all visitors same country

Other Umami errors

• Umami Not Tracking Visitors (No Data Showing)
• Umami Blocked by Ad Blockers (uBlock Origin, Brave)
• Umami v3 Upgrade: MySQL Not Supported
• Umami Migration Failed (Prisma P3009 / P3018 Error)
• Umami Docker "Unable to Connect to the Database"
• Umami Default Login and Forgot Password Reset
• Umami Custom Events Not Showing
• How to Exclude Your Own Visits in Umami