DNS-hole widget not working

sebingel commented 2 months ago

Environment

Docker

Version

0.15.2

Describe the problem

I have an app with pi-hole integration on my dashboard. It's showing the green bubble. But the DNS-hole widgets are not working.

Both, homarr and pi-hole, are running as docker containers. homarr is in a custom docker network and pi-hole is in the docker hosts network. They cannot communicate directly. Communication is established by a reverse proxy residing in both networks. As far as I can tell, communication is working, since the app on the dashboard is showing the green bubble. But as you see in my screenshots, both dns-hole widgets don't work.

Unfortunately, I don't even know how to start debugging this as the homarr log does not show anything related.

Logs

Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 1.78s.
Starting production server...
Listening on port 7575 url: http://85030d074bae:7575
ℹ Local icons repository directory exists and contains 0 icons

Context

dashboard allgemein integration

Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

github-actions[bot] commented 2 months ago

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

diogovalentte commented 1 month ago

I don't know if you're still facing this issue OP, but it happened to me for some time. Turns out the API key that I got from Pihole was constantly changing because I didn't set a password for my pihole container using the WEBPASSWORD environment variable. So the password and API key were randomly generated every time the container was restarted. With a fixed password this doesn't happen.

sebingel commented 3 weeks ago

Thanks for the reply. Unfortunately, this is not the problem. I set the WEBPASSWORD env var on my container. And I can recreate this behavior with the current API key.

ajnart / homarr