Pi-Hole integration cannot be connected
Pi-Hole Version: 6.0.6
Homarr Version: 1.17.0
Certificate of PiHole is added under Certificates.
API App password is entered correctly. (copy and paste)
Attempted URLs:
http://pi.hole
https://pi.hole
http://pi.hole:443
https://pi.hole:443
Log entry from the web interface:
info Dispatching request https://pi.hole/api/info/version (5 headers)
Tried to read the version directly in the container via curl and authentication via the post worked.
What am I doing wrong? How can I integrate the integration correctly?
4 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?
Log:
2025-04-21T14:02:03.248Z 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/626.js:107:5069
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/626.js:107:7029
at async /app/apps/nextjs/.next/server/chunks/626.js:83:797386
caused by TypeError: fetch failed
at e.exports.hd (/app/apps/nextjs/.next/server/chunks/279.js:8:33270)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Array.sN (/app/apps/nextjs/.next/server/chunks/6739.js:6:16603)
at async sL (/app/apps/nextjs/.next/server/chunks/6739.js:6:22226)
at async s1 (/app/apps/nextjs/.next/server/chunks/6739.js:6:26061)
at async /app/apps/nextjs/.next/server/chunks/6739.js:6:29182
at async p.middlewares (/app/apps/nextjs/.next/server/chunks/626.js:98:395155)
at async u (/app/apps/nextjs/.next/server/chunks/626.js:101:68)
at async u (/app/apps/nextjs/.next/server/chunks/626.js:101:68)
at async u (/app/apps/nextjs/.next/server/chunks/626.js:101:68)
caused by Error: unable to verify the first certificate code="UNABLE_TO_VERIFY_LEAF_SIGNATURE"
at TLSSocket.onConnectSecure (node:_tls_wrap:1679:34)
at TLSSocket.emit (node:events:518:28)
at TLSSocket._finishInit (node:_tls_wrap:1078:8)
at ssl.onhandshakedone (node:_tls_wrap:864:12)
at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17)
Is there already a solution ? I have exactly the same issue
The above error occurs for https because the self signed certificate is
- 1. either not trusted
- 2. or the hostname is not matching the certificate altnames
In the above it should be caused in a first step by the first one, see https://homarr.dev/docs/management/certificates/ on how to add trusted certificates. We are currently working on a feature that should allow to show a modal if certificate errors occur with different options, stay tuned!
Certificates | Homarr documentation
On this page you can manage your trusted certificates.