Hi @frenck, Is it possible to resolve any public domain name to my local network ip address using this pi.hole add-on dns feature?
Thanks,
Hello, my snapshot are getting bigger because of pi-hole.
I tried to flush the logs but still 500mo just for the addon.
Do you have any idea how to make it smaller ? Is there a way to clean everything, I donāt mind losing the logs.
Thanks,
Please do not do that and donāt recommend that to people either. We should not recommend people to go into the lower levels of the system and fool around with it. In the end, that will cause you issues.
As you are using hass.io, you can try this: log into your home assistant using ssh (with ssh & web terminal add-on) and use this command: ha supervisor repair
Ok post deleted. I thought this could help as it was the only solution for me (when i looked into it more than a year ago) to overcome the lack of loopback capability on my router.
Thanks for your warning and your job on HA.
How this command will help me reduce the size of pi-hole ?
Sounds like a bug that needs to be addressed. Normally a scheduled tasks should take care of that. Please report it on the GitHub repo of the add-on.
It will flush some old data for all add on by doing some repair. Saved 3Gb using this command. And my snapshot went from 80mb to only 25mb
I tried, didnāt save me anything in my case 
I uninstalled and reinstall the addon, everything is ok now.
Alright. So i have a Pi4 and want to run Hassio with the PiHole add-on.
Iāve set everything up and it looks like itās working with a few problems:
In PiHole it says under settings thats itās Ipv4 is 192.168.1.3 (example). The host, the Pi4 is 192.168.1.4
The 192.168.1.3 is unfindable in the whole network. Is this a normal thing? Cause i want that IP to be assigned as DNS1 by my router, so that all seperate deviced get monitored by the PiHole and i get a nice view per device.
Might be something stupid, but canāt get around it.
Release v4.1.0
This is a general maintenance release, containing a lot of internal upgrades and fixes.
Changes
-
Fixes issues with HTTP header checking (#89) -
Remove virtual host configuration (#90) -
Fix admin/queries.php for ingress users (#97)
-
Fix admin/queries.php for direct users (#98)
-
Fix error log path to /dev/stderr (#91) -
Update documentation on how to integrate with Home Assisā¦ (#102) -
Upgrades Pi-hole web interface to v4.3.2 (#107) -
Removed coffee patch
-
Updated fix killall brain damage patch
-
Update add-on installation instructions
-
Fixes Markdownlint warnings -
Updates maintenance/license year to 2020 -
Funding adjustments -
Fixes some spelling and grammar
-
Upgrades gcc to 9.2.0-r3
-
Upgrades musl-dev to 1.1.24-r0
-
Upgrades nettle-dev to 3.5.1-r0
-
Upgrades sqlite to 3.30.1-r1
-
Upgrades psmisc to 23.3-r0
-
Upgrades openssl to 1.1.1d-r3
-
Upgrades bind-tools to 9.14.8-r5
-
Upgrades logrotate to 3.15.1-r0
-
Upgrades perl to 5.30.1-r0
-
Upgrades git to 2.24.1-r0
-
Upgrades lua-resty-http to 0.15-r0
-
Upgrades ncurses to 6.1_p20191130-r0
-
Upgrades procps to 3.3.16-r0
-
Hot patch FTL for nettle 3.5 compatibility
-
Update Home Assistant integration instruction
-
Upgrades nginx to 1.16.1-r6
-
Update add-on documentation to use new YAML configuration format
-
Re-branding
-
Update add-on config with new password & list features
-
Updates for upstream Supervisor changes
-
Fix broken Home Assistant DNS servers in list
-
Admin scripts rewrite (#123)
-
Upgrades add-on base image to v7.0.2
-
Add access control to api.conf (#114)
-
Upgrades libxml2 to 2.9.10-r2
-
Upgrades ncurses to 6.1_p20200118-r2
-
Upgrades php7 to 7.3.15-r0
-
Upgrades sudo to 1.8.31-r0
-
Upgrades Pi-hole core to v4.4
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work:
https://github.com/sponsors/frenck or https://patreon.com/frenck
Just updated to the latest version (4.1), and my pi-hole sensors are all reporting āunavailableā.
Iām also unable to use the following command, which previously worked perfectly:
curl -X GET 'http://<local_address>:4865/admin/api.php?status'
Instead of returning the expected status, Iām getting a 403 Forbidden error from nginx.
Did something change, and I need to tweak my config, or has something gone wrong with the add-on itself?
1 Like
Iāve got the same trouble.
1 Like
I probably have the same problem. There are many messages in the logs.
Logger: homeassistant.helpers.template
First occured: 12:00:11 (315 occurences)
Last logged: 14:42:25
Error parsing value: āvalue_jsonā is undefined (value:
403 Forbidden403 Forbidden
nginx , template: {{ value_json.status == 'enabled' }})
1 Like
Iāve been having the same issue here. My pi-hole sensors are unavailable and I canāt enalbe / disable it as before after this update.
1 Like
Release v4.1.1
This is a bug fix release.
Changes
-
Update community forum links
-
Bypass HTTP origin
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work:
https://github.com/sponsors/frenck or https://patreon.com/frenck
FWIW, release 4.1.1 does not resolve the problem of Pi-Hole sensors all responding with āunavailableā, as reported by me and several other folks here.
Not a complaint, just a report. (Though I do want to get the sensors and curl access working again.)
The release notes donāt state that either, so that would be correct
1 Like