HELP WITH PI-HOLE INTEGRATION
i just cant get the pi-hole integration working no matter what . for starters the api key key retrieval isnt easy and i was told to use the app password as api key or somehting but i did that still it doesnt work .please help
49 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
β οΈ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
CAN YOU PLEASE POST THE DATA AS THE BOT ASKS YOU TO?
TRUENAS SCALE
HOMMER VERSION-latest build
its deployed via potrainer stacks
browser is ZEN browser based on firefox.
Please read the message again.
latest is not a valid version
And please provide more details on your PiHole setup. Where is your PiHole running? What URL did you provide? How do you logs look like?basically when i hit connect this message appears
others above that aren't necessary logs i think . the issue seems to be with the api key
this is supposed to be the key right?
1.15.0
i hope this answers it!
@Manicraft1001 ?
hey man are you alive?
Yes
This is not the log. Please post the log.
sent
never mind
20720 is the port your UI is running on?
How do you run PiHole and Homarr? Both as apps on TrueNAS?
yes pi-hole as an app
and hommar inside portainer
hommar detects every other app
integration in portainer and beyond it are also fine
just the integration with pi-hole isn't working
docs say that Homarr using old API Key connection to Pihole, but Pihole don`t use it anymore
Use the App password
still not working vidget
nah, dont work
Please post your logs
Is not this, is the password you set at the beggining. You can reset it with
STILL widget shows zeros
I can't help you if you don't post your logs
Hello @Kirill π , were you able to resolve this? Do you need any further assistance?
would be great that if someone helps me)
Ok, you still haven't posted any logs. Please post your logs. We cannot help you without them
once again, pihole changed authorization, now api key is not working, what exact logs do I need to show?
Seriously? How often do they make breaking changes in their API??? Do you have a source / link / release notes for that, before we look into the API docs? Can you submit a new issue if the API really has a breaking change
my screenshot with zeros in previously fluent working widget
this one logs or another?
You are using 0.15.10 and so it's not supported. Migrate to v1 https://homarr.dev/blog
if you want to work with pi-hole v6
oh, thanks!
wow new board! fancy!))
still nothing
and logs is simply black blank screen
why all of them are offline? they literally up and working!
Post the logs from docker or enable websockets on your proxy to view them in the ui
2025-04-28T19:28:53.854Z info: Dispatching request http://192.168.8.102/admin/api/info/version (5 headers)
2025-04-28T19:28:53.858Z error: tRPC Error with mutation on 'integration.create'
at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:4403)
at Object.onError (/app/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:3561)
at /app/apps/nextjs/.next/server/chunks/4566.js:106:5069
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/4566.js:106:7029
at async /app/apps/nextjs/.next/server/chunks/4566.js:94:2274661
caused by TypeError: fetch failed
at e.exports.hd (/app/apps/nextjs/.next/server/chunks/9903.js:411:63060)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Array.iO (/app/apps/nextjs/.next/server/chunks/8148.js:6:16661)
at async iL (/app/apps/nextjs/.next/server/chunks/8148.js:6:20704)
at async i1 (/app/apps/nextjs/.next/server/chunks/8148.js:6:24539)
at async /app/apps/nextjs/.next/server/chunks/8148.js:6:27660
at async p.middlewares (/app/apps/nextjs/.next/server/chunks/4566.js:97:416839)
at async u (/app/apps/nextjs/.next/server/chunks/4566.jsπ―68)
at async u (/app/apps/nextjs/.next/server/chunks/4566.jsπ―68)
at async u (/app/apps/nextjs/.next/server/chunks/4566.jsπ―68)
caused by Error: connect ECONNREFUSED 192.168.8.102:80 errno="-111" code="ECONNREFUSED" syscall="connect" address="192.168.8.102" port="80"
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)
Is your pihole running on this ip on port 80? May it run on https instead? can you check that
ping not workinkg in any variation
Okay it's a network problem, so either wrong port or docker network
naah probably its mine self signed certificate
and this without https
what does error 111 maen?
The relevant part is "ECONNREFUSED", it means that it cannot connect
And the above error with HTTPS means that you need to upload the PiHole certificate.
See https://homarr.dev/docs/next/management/certificates/#pi-hole-v6 on how to get the self signed certificate for pihole v6
Certificates | Homarr documentation
On this page you can manage your trusted certificates.
@Kirill π any update? Can we mark this as resolved?