Latest v5.15.1 and further 2022-10-10 updates not refreshed in webinterface (version information not in sync)

[bcutter]

Versions

• Pi-hole version is v5.13 (Latest: v5.13)
• AdminLTE version is v5.16 (Latest: v5.16)
• FTL version is v5.18.2 (Latest: v5.18.2)

Platform

• OS and version: Raspberry Pi OS Bullseye

• Platform: Raspberry Pi

Expected behavior

After updating with pihole -up the new version of all 3 components is updated on all places.

Actual behavior / bug

The version information is updated correctly here:

• ✔cli (pihole -v and pihole -up)
• ✔PADD (see screenshot below)

But it isn't here:

• ❌webinterface (see screenshot below)
• ❌Home Assistant by using the official Pi-Hole integration

Steps to reproduce

Steps to reproduce the behavior:

1. Update to latest version using pihole -up
2. Check version information at various places

Screenshots

Webinterface

PADD

Home Assistant

Additional context

• Probably an API issue?
• Did a pihole restartdns already.
• Refreshed browser cache, used another browser and machine - same output.

==> Update after looking at the PADD screenshot: various status information is not provided correctly. See the screen telling DNS server is off. At the same time pihole status gives

  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

Please feel free to move this issue to the right component (GitHub project), maybe it's a core or FTL issue.

[bcutter]

After searching the forums a bit deeper:

https://discourse.pi-hole.net/t/pihole-v-says-the-system-is-up-to-date-but-the-web-interface-indicates-updates-needed/58475

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pihole-v-says-the-system-is-up-to-date-but-the-web-interface-indicates-updates-needed/58475/3

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/padd-broken-after-latest-updates/58461/11

[bcutter]

After looking at https://discourse.pi-hole.net/t/padd-broken-after-latest-updates/58461 I am pretty sure this is the root cause for the underlying API issue:

pi-hole/FTL#1445

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/pihole-v-says-the-system-is-up-to-date-but-the-web-interface-indicates-updates-needed/58475/7

[yubiuser]

Workaround is to run pihole updatechecker

[bcutter]

Fixed (for now) by https://discourse.pi-hole.net/t/pihole-v-says-the-system-is-up-to-date-but-the-web-interface-indicates-updates-needed/58475/5.

Leaving it open and up to devs to close it once the root cause has been fixed.

[yubiuser]

PADD issue fixed by pi-hole/PADD#259

[dschaper]

A debug log before any changes would have been the best way to help us find if this is a bug or not.

[bcutter]

That's too late I guess. But for sure experts can downgrade and provoke the behavior again - or is it an edge case?

Off-topic: I don't like the debug logs as they contain really sensitive information (which takes a lot of time to manually identify and remove them), doesn't matter how few people for how short time have access to it. For example I doubt having my full domains list with all whitelisted and blacklisted domains is necessary for debugging such an issue.

[dschaper]

Unable to reproduce. I understand your concern about privacy. We don't have a lot of time to ask questions back and forth so we use the log to assist you. It states pretty clearly in the issue template that we will close issues tickets that omit information we need to debug so I'll close this out and you can use the community support forums to research further.

[rdwebdesign]

I understand your privacy concern. I also know users privacy is really respected by devs.

For example I doubt having my full domains list with all whitelisted and blacklisted domains is necessary for debugging such an issue.

The debug log was designed to show information needed to fix A LOT of different issues.
Of course, not all information would be relevant to every issue, but it is the best way to avoid dozens of questions before we start to understand each user system.

Without it, we can't help as efficiently as we could if we had the log.

We help users on our free time and we don't have a lot to spare. Feel free to seek help on Discourse Forum.