Pihole -v says the system is up to date but the web interface indicates updates needed

mattw · October 11, 2022, 3:09pm

Please follow the below template, it will help us to help you!

*If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using

I am running apache web server on this box to support ups units and other software.
This pihole seems to be working fine, just the version on the web page seems wrong.
Forgot to add system has been fully rebooted and I have tested in a browser that has never had the page cached.

Expected Behaviour:

I am running pihole on a Pi 4 and have been for ever, this is a general purpose box that runs many things.
OS - Buster / Raspbian GNU/Linux 10
Kernel - 5.10.103./v7l+

I expected the web interface to reflect the updated state.

Actual Behaviour:

pi@genpi:~ $ pihole -v
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)

Web interface:

Debug Token:

https://tricorder.pi-hole.net/zTFDjpiD

rdwebdesign · October 11, 2022, 7:26pm

The web interface should see the same info as pihole -v.

Can you please try to clean your browser cache and try again?

bcutter · October 11, 2022, 8:03pm

Seeing the same. See also

github.com/pi-hole/AdminLTE

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

opened 08:02PM - 11 Oct 22 UTC

bcutter

### Versions - Pi-hole version is v5.13 (Latest: v5.13) - AdminLTE version i…s 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 ![grafik](https://user-images.githubusercontent.com/13799156/195186215-e5e9c7b0-9268-4bed-8048-d06c67d7407d.png) PADD ![grafik](https://user-images.githubusercontent.com/13799156/195186470-fa4b8da6-e2ae-4d1d-9c4c-6c1164e54fee.png) Home Assistant ![grafik](https://user-images.githubusercontent.com/13799156/195186652-9731deb3-ca55-4ee4-8c99-c21168d20e15.png) ### 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 · October 11, 2022, 8:09pm

Here's some progress:

And the root cause is likely this change:

github.com/pi-hole/PADD

Get API port from pihole-FTL.conf instead of port file

pi-hole:development ← pi-hole:no_port

opened 07:25PM - 27 Sep 22 UTC

yubiuser

+23 -1

**What does this PR aim to accomplish?:** We removed the `pihole-FTL.port` fi…le here: https://github.com/pi-hole/FTL/pull/1445. The file was used by `PADD` to get the current API port to communicate with `FTL`. With this PR `PADD` now tries to read the port from `pihole-FTL.conf` the same as we do it in https://github.com/pi-hole/pi-hole/pull/4945 --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code and I have tested my changes. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) --- - [x] I have read the above and my PR is ready for review. _Check this box to confirm_

yubiuser · October 11, 2022, 8:12pm

This PR removed the in 10 minutes check for updates

github.com/pi-hole/pi-hole

Remove cronjob that checks local versions every 10 minutes - only check when required

pi-hole:development ← jpgpi250:development

opened 01:02PM - 24 Sep 22 UTC

jpgpi250

+9 -3

Signed-off-by: jpgpi250 <jpgpi250@gmail.com> ## Thank you for your contributi…on to the Pi-hole Community! Please read the comments below to help us consider your Pull Request. We are all volunteers and completing the process outlined will help us review your commits quicker. **Please make sure you** 1. Base your code and PRs against the repositories developmental branch. 2. [Sign Off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits as we enforce the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions --- - **What does this PR aim to accomplish?:** see https://discourse.pi-hole.net/t/pi-hole-stoppen-zwecks-backup/57989/10 - eliminate updatechecker local from the pihole cronjob - add updatecheck to piholeDebug.sh - check if api.github.com returns a valid IP address - **How does this PR accomplish the above?:** changed: - pihole.cron - piholeCheckout.sh - piholeDebug.sh - updatecheck.sh - **What documentation changes (if any) are needed to support this PR?:** none **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code and I have tested my changes. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) --- - [x] I have read the above and my PR is ready for review. _Check this box to confirm_

But we still call the relevant function after any update

github.com

pi-hole/pi-hole/blob/17779bad94be15cf07ea9f258ce84a07fbe294f7/advanced/Scripts/update.sh#L218-L221


      
          if [[ "${FTL_update}" == true || "${core_update}" == true || "${web_update}" == true ]]; then
              # Force an update of the updatechecker
              /opt/pihole/updatecheck.sh
              /opt/pihole/updatecheck.sh x remote

Please run pihole updatechecker and see if this fixes it

yubiuser · October 11, 2022, 8:13pm

The PADD stuff is unrelated to the wrong update notification in the web interface.

bcutter · October 11, 2022, 8:16pm

I can confirm running pihole updatechecker fixed the webinterface (and other places like Home Assistant).

grafik

Do we need to run that after every update by our own or...?
Would you mind taking care of Latest v5.15.1 and further 2022-10-10 updates not refreshed in webinterface (version information not in sync) · Issue #2396 · pi-hole/AdminLTE · GitHub ?

Strange I hit two issues, current open one is the PADD part.

yubiuser · October 11, 2022, 8:17pm

Not if we find the root of this bug...

mattw · October 11, 2022, 8:23pm

I re-ran pihole -up a moment ago, no new versions found. I also cleared cache in my browser and tried a browser that I had not logged into pihole with and both still show the need to update.

bcutter · October 11, 2022, 8:24pm

See:

mattw · October 11, 2022, 8:28pm

I did not realize pihole updatechecker was a thing... ran it and it is now reporting properly.

bcutter · October 11, 2022, 8:30pm

Well it was in one of the last posts before yours, so... reading would have been an option
Anyway, glad to see this workaround fixed it for you too.

mattw · October 11, 2022, 8:32pm

Thanks, I did read all of the posts... I did not realize that was a command, not listed in the pihole -?. I thought it was an implication to run pihole -up!

DanSchaper · October 11, 2022, 9:36pm

Can you show your apache configuration for the web interface?

chrislph · October 11, 2022, 10:08pm

I've had possibly the same problem, the other way around, with the previous two releases. The new release would be announced but no matter what I did in the interface I couldn't make Pi-hole see it. The footer remained unchanged, Clearing cache and cookies and logging back in made no difference, implying some Pi-hole checking logic instead.

Doing pihole -up saw the new versions and updated as expected. Prior to those releases, if I saw a new announcement and simply reloaded the web page or even just clicked a sidebar link I would instantly be seeing the red Update available! text in the footer.

Not sure if related but about since the same time pihole -d always shows Core and Web as the latest version but always in yellow (with a green master branch below) with a URL next to it for how-do-i-udpate-hole, as if it thinks they're not up to date. FTL always shows in green with a green master.

Standard Pi-hole install, no Apache.

yubiuser · October 12, 2022, 7:50pm

We only update the remote version info once every 24 hours (and after a handful of command) to avoid steady connection to GitHub. See That Time We DDoSed GitHub – Pi-hole.

I'll take a look.

yubiuser · October 12, 2022, 8:01pm

There is room for improvement/bug.

mattw · October 12, 2022, 8:23pm

I could, but it is pretty ugly. I use Apache for pi-hole, nutstatus, smokeping, webmin and if memory serves... a couple of other things. I found a note a few years back on how to setup Apache for pihole as I did not have enough memory on the old 3b to run both webservers, samba, smokeping, nut and other things at the same time. Now on the pi4 that really is not the case.

yubiuser · October 13, 2022, 1:38pm

github.com/pi-hole/pi-hole

Remove check for latest component version in debug log

pi-hole:development ← pi-hole:improve_debug

opened 01:35PM - 13 Oct 22 UTC

yubiuser

+16 -42

**What does this PR aim to accomplish?:** 1. Remove the check of the latest a…vailable version of each component. See discussion blow. 2. Remove the checkout hint. If users are so advances that they are on custom branches they should know how to `checkout` or will ask anyway. ``` *** [ DIAGNOSING ]: Core version [✓] Version: v5.13 [i] Remotes: origin https://github.com/pi-hole/pi-hole.git (fetch) origin https://github.com/pi-hole/pi-hole.git (push) [i] Branch: development [i] Commit: v5.13-1-g89c0706a *** [ DIAGNOSING ]: Web version [✓] Version: v5.16 [i] Remotes: origin https://github.com/pi-hole/AdminLTE.git (fetch) origin https://github.com/pi-hole/AdminLTE.git (push) [i] Branch: 99 [i] Commit: v5.16-5-g8abfde2e *** [ DIAGNOSING ]: FTL version [✓] Version: vDev-14cffae [i] Branch: update/dnsmasq [i] Commit: 14cffae ``` --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 5. I have commented my proposed changes within the code and I have tested my changes. 6. I am willing to help maintain this change if there are issues with it later. 7. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 8. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) --- - [x] I have read the above and my PR is ready for review. _Check this box to confirm_

system · November 3, 2022, 1:38pm

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.