Skip to content

PADD script error when connecting to a VM hosted PiHole instance. #458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
acolwill opened this issue Apr 4, 2025 · 6 comments
Open

PADD script error when connecting to a VM hosted PiHole instance. #458

acolwill opened this issue Apr 4, 2025 · 6 comments

Comments

@acolwill
Copy link

acolwill commented Apr 4, 2025

Describe the bug
PADD running on a device when connecting to a PiHole instance running in a VM throws script errors continuously
The line in the script it's relating to is for printing the CPU temp (line 417).

To Reproduce
Steps to reproduce the behavior:

  1. Run PiHole in a VM.
  2. Install PADD on a device and point to the VM'd PiHole instance.

Expected behavior
Recognise the missing CPU temperatures and ignore... or perhaps a start-up switch to ignore CPU temp?

Screenshots
Image

Additional context
PiHole VM is Ubuntu Server 24.04 minimised, running on HyperV in Windows Server 2025.

@mwoolweaver
Copy link
Contributor

try the version on the development branch

https://raw.githubusercontent.com/pi-hole/PADD/refs/heads/development/padd.sh

#438 shows a fix in place on the development branch

@acolwill
Copy link
Author

acolwill commented Apr 4, 2025

Getting two errors now... on line 410 and 415.

Image

@mwoolweaver
Copy link
Contributor

mwoolweaver commented Apr 4, 2025

Probably need the development branch of FTL as well

#453

@acolwill
Copy link
Author

acolwill commented Apr 4, 2025 via email

@yubiuser
Copy link
Member

yubiuser commented Apr 4, 2025

@mwoolweaver is correct.

The development branch of PADD fixes your issue with PR #428.
However, it currently requires also the development branch of FTL. So everything will be sorted in the next release.

@mwoolweaver
Copy link
Contributor

next release.

Soon™

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants