Error with logs

[joejsullivan]

Hi - have a problem getting the Chrome extension to display details. I see this error below. I do have IPv6 enabled as well.

Error: Client-IP konnte nicht ermittelt werden (keine Log-Entry gefunden).

Also - is it normal that only the primary node can be used for the API token in a cluster?

Technitium version Version 15.0.1

Thanks,
Joe

[ThreeM-MMM]

Hi, I’m a bit late and on vaccation, but I still wanted to at least reply.

Problem 1:

This can happen with IPv6. Many systems use temporary/privacy IPv6 addresses that rotate. The extension caches the detected client IP and filters Technitium query logs by that exact IP — so if your IPv6 address changes, the log filter may no longer match.

Quick workaround (please try)

1. Open chrome://extensions/
2. Enable Developer mode
3. Find Technitium Adblock Control → click Service worker → Inspect
4. In the console, run:

chrome.storage.local.remove(["clientIpAddress", "clientIpDetectedAt"]);

5. Close the console, reload the extension (or just reopen the popup) and try again.

This should forces the extension to re-detect your current client IP and should make the log entries appear again.

Could you try this and let me know:

• whether it fixed the issue, and
• if possible, whether your device is using IPv6 privacy/temporary addresses?

Thanks :)

---

For your second question: Yes — in a Technitium cluster the primary node is the writable authority for cluster-wide configuration changes. API tokens created on the primary are synchronized across the cluster and should generally be valid on all nodes, but write operations should target the primary (secondary nodes are effectively read-only for many management actions).

---

I’m currently still on vacation for another three weeks. As soon as I’m back, I’ll look into the IPv6 issue and fix it.