failed to lookup address information - DNS resolution issue in ChirpStack container

[Marcos_Figueiredo_Ju]

Hi everyone,

I’m running ChirpStack v4 using the official chirpstack/chirpstack:4 Docker image in a local Docker Compose setup.

Everything works fine — MQTT, PostgreSQL, Redis — but I keep getting frequent errors in the ChirpStack logs like this:

ERROR chirpstack::api::internal: Reading frame-log returned error: failed to lookup address information: Try again
ERROR chirpstack::api: Log request error error=failed to lookup address information: Try again

The system works and my gateway connects (I see uplinks), but the logs and event logs don’t load in the web UI.

What I’ve verified:

• Docker container can ping external IPs (ping 8.8.8.8)
• Container can resolve internal Docker services (like mosquitto, postgres)
• I added dns: [8.8.8.8, 1.1.1.1] to the chirpstack service in docker-compose.yml
• geo_resolver is set to enable=false in chirpstack.toml

Still, the logs report name resolution errors like it’s trying to do an external DNS lookup and failing.

My Setup:

• Ubuntu 22.04 host
• Docker + docker-compose
• ChirpStack 4.12.1
• DNS resolvers seem fine on the host

Does anyone know which ChirpStack component is doing DNS lookups in the API log section, and what name it might be trying to resolve?
Any suggestions to debug or fully resolve this would be really appreciated.

Thanks in advance!

[Liam_Philipp]

Hard to tell with just those two errors, doesn’t even show what api calls are being made. My hunch however is that if your UI logs and event logs don’t work, this is likely a redis issue, as those are whats responsible for holding the most recent uplinks for graphs and event feeds. If not, it must be a more general issue with Chirpstack’s internal API (the web UI is just an http client for Chirpstack’s gRPC API).

Maybe try setting your logs to trace? And were you purely looking at chirpstack logs there or did you do a docker-compose logs -f?