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
Thanks for the report. Since v0.4.2 the Coolify compose downloads the geo database itself, and the collector refuses to start without it, so if the collector is up the database is loaded. The likelier cause is the address the collector sees: Coolify's Docker network has no IPv6, so every visitor arriving over IPv6 reaches the proxy as 172.18.0.1 (coollabsio/coolify#3436), and a private address has no country.
Could you share: the log of the geoip container and the first line of the collector's log; the branch or tag Coolify tracks; whether your domain has an AAAA record; where the test visits came from (IPv6 network, LAN, VPN); and whether anything like Cloudflare sits in front of Coolify. Turning on the Traefik access log in Coolify's proxy settings and checking ClientHost settles it.
If it is the IPv6 case, enabling IPv6 on the Coolify network (steps in that issue) or dropping the AAAA record fixes it. We will document this trap either way.
Activity
Uaghazade1 commentedon Sep 10, 2026
Thanks for the report. Since v0.4.2 the Coolify compose downloads the geo database itself, and the collector refuses to start without it, so if the collector is up the database is loaded. The likelier cause is the address the collector sees: Coolify's Docker network has no IPv6, so every visitor arriving over IPv6 reaches the proxy as 172.18.0.1 (coollabsio/coolify#3436), and a private address has no country.
Could you share: the log of the
geoipcontainer and the first line of the collector's log; the branch or tag Coolify tracks; whether your domain has an AAAA record; where the test visits came from (IPv6 network, LAN, VPN); and whether anything like Cloudflare sits in front of Coolify. Turning on the Traefik access log in Coolify's proxy settings and checking ClientHost settles it.If it is the IPv6 case, enabling IPv6 on the Coolify network (steps in that issue) or dropping the AAAA record fixes it. We will document this trap either way.
fix(selfhost): platform blueprints pin v0.6.0, and the IPv6 country t…
bridgerahul commentedon Sep 19, 2026
No reply, so closing this as documented rather than fixed.
v0.8.0 writes the IPv6 case down in
SELF-HOSTING.mdand in both platform guides, so the next person meets the explanation before the card does.If it still shows Unknown on your install, reopen with the two things above and we will keep digging.