Unable to connect Pi-Hole

Hi Even with the latest certificate changes, I'm unable to connect my pihole:
Solution:
This is a validation improvement that we added when you upload certificates. You could crash Homarr if you uploaded broken or unsupported files. This is not related to the error you're experiencing
Jump to solution
15 Replies
Cakey Bot
Cakey Bot13h ago
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?
CrazyWolf13
CrazyWolf13OP13h ago
No description
Manicraft1001
Manicraft100113h ago
!qa required_data
Cakey Bot
Cakey Bot13h ago
Thank you for your question. Our support team has noted that your request does not meet the minimum required data so we are unable to answer your question. Please provide: - your Homarr logs - your setup configuration (eg. docker compose, docker run, helm chart, screenshot, ...) - A detailed description of your problem or question with additional images where necessary - Your operating system - Version of Homarr (do not say latest! say 0.15.2, ...) Failure to comply with this will result in a permanent closure of your support request.
CrazyWolf13
CrazyWolf13OP13h ago
on it 🙂
Manicraft1001
Manicraft100113h ago
I briefly checked. We have not changed the PiHole integration between 1.17.0 and 1.18.0. Are you sure, that 1.18.0 causes it? Have you maybe upgraded PiHole? If yes, can you confirm by rolling back and checking there?
CrazyWolf13
CrazyWolf13OP13h ago
So I still have my certs imported: I try to connect pihole: Here the logs:
Apr 25 21:36:41 homarr run_homarr.sh[6650]: 2025-04-25T19:36:41.623Z info: Dispatching request http://10.10.20.8/rpc.php (8 headers)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: 2025-04-25T19:36:41.660Z error: tRPC Error with mutation on 'integration.create'
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.onError (/opt/homarr/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:4158)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.onError (/opt/homarr/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:3316)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at /opt/
Apr 25 21:36:41 homarr run_homarr.sh[6652]: caused by Error: Hostname/IP does not match certificate's altnames: IP: 10.10.20.15 is not in the cert's list: code="ERR_TLS_CERT_ALTNAME_INVALID" reason="IP: 10.10.20.15 is not in the cert's list: " host="10.10.20.15"
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.checkServerIdentity (node:tls:316:12)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at TLSSocket.onConnectSecure (node:_tls_wrap:1689:27)
Apr 25 21:36:41 homarr run_homarr.sh[6650]: 2025-04-25T19:36:41.623Z info: Dispatching request http://10.10.20.8/rpc.php (8 headers)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: 2025-04-25T19:36:41.660Z error: tRPC Error with mutation on 'integration.create'
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.onError (/opt/homarr/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:4158)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.onError (/opt/homarr/apps/nextjs/.next/server/app/api/trpc/[trpc]/route.js:1:3316)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at /opt/
Apr 25 21:36:41 homarr run_homarr.sh[6652]: caused by Error: Hostname/IP does not match certificate's altnames: IP: 10.10.20.15 is not in the cert's list: code="ERR_TLS_CERT_ALTNAME_INVALID" reason="IP: 10.10.20.15 is not in the cert's list: " host="10.10.20.15"
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at Object.checkServerIdentity (node:tls:316:12)
Apr 25 21:36:41 homarr run_homarr.sh[6652]: at TLSSocket.onConnectSecure (node:_tls_wrap:1689:27)
No description
No description
CrazyWolf13
CrazyWolf13OP13h ago
Oh really, I though Meierschlumpf fixed the certs issue I was having "certificates: Added certificate validation to prevent crashes and improve UX"
Manicraft1001
Manicraft100113h ago
I doubt this was introduced in 1.18.0. It means that your certificate was never signed for that IP. Use http, sign your own certificate that includes your IP or use the FQDN that this cert was signed for
Solution
Manicraft1001
Manicraft100113h ago
This is a validation improvement that we added when you upload certificates. You could crash Homarr if you uploaded broken or unsupported files. This is not related to the error you're experiencing
CrazyWolf13
CrazyWolf13OP13h ago
yeah apologies, that was me being excited too early lol, actual PR pr is not made yet: https://github.com/homarr-labs/homarr/issues/2553
GitHub
feat: add checkboxes to remove certificate checks · Issue #2553 ·...
Describe the feature you'd like to request Add two new checkboxes to the integration creation page Checkbox to ignore certificate check altogether with rejectUnauthorized: false Checkbox to dia...
Manicraft1001
Manicraft100113h ago
Correct 👍 You can deactivate verification completely though using the NODE_TLS_REJECT_UNAUTHORIZED environment variable. It should work but is very unsafe and will disable verification for everything. It's comparable to falling back entirely to HTTP and removing all security checks. So if possible, try to fix your certificate. It is the correct solution in the first place.
CrazyWolf13
CrazyWolf13OP13h ago
I'd definitely agree, but as it's handled entirely by pihole, I will a be not the only person having this problem and b don't really wanna pick into pihole here. Normally that's definitely what I'd do. sounds good, but imo pihole widget is not that important for such a security compromise 🙂
Manicraft1001
Manicraft100113h ago
See https://gist.github.com/kaczmar2/e1b5eb635c1a1e792faf36508c5698ee I'd argue that it's the most critical part of your network. - An attacker could leverage your certificate ignore to hijack the request and grab your credentials - Then they manipulate PiHole to resovle your domains to a different man in the middle host, which forwards the requests again so you don't notice anything - Lastly, they can do whatever they want because they have now gained full control of your DNS and thus likely also of your network.
CrazyWolf13
CrazyWolf13OP13h ago
yeah definitely, I'll try to get some answer from pihole, whether this can be done easily or not.

Did you find this page helpful?