Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't control PiHole using IP #21

Open
morficus opened this issue Aug 23, 2023 · 7 comments
Open

Can't control PiHole using IP #21

morficus opened this issue Aug 23, 2023 · 7 comments

Comments

@morficus
Copy link

Hello there!
I've been using this plugin since May with no issues until about a week ago or so.

I recently noticed the ⚠️ would appear on the PiHole buttons for a few seconds, then disappear. After a bit of experimentation... I was able to fix it by configuring the plugin to use the DNS name rather than the IP (which is how it was set up since May).

This seems to be a similar issue reported in this comment, which is where I got the idea of trying the hostname.

System details:

  • MacOS 13.4.1(c)
  • Stream Deck firmware 1.01.000
  • Pi-hole v5.17.1
  • Yes, I can access the PiHole using the IP address from the host machine
@warinthestars
Copy link

I am also having this issue.
Windows 10 - 22H2
Firmware: 1.30
Pihole - 5.17.1

@Firehed
Copy link

Firehed commented Sep 21, 2023

I too ran into this. Out of a hunch I checked the source code, and it didn't look like anything strange was occurring.

What I observed was that changing from ip to host fixed the issue, but subsequently changing BACK to the IP doesn't seem to have reintroduced the issue. I suspect that #9 may have introduced an upgrade bug where the new protocol setting had no value for older installations (this lines up with your timing!), and the act of changing anything got it populated so it could make correct requests again.

If you've run into this and have not yet tried changing the settings, making a copy of your stream deck config and showing the section that has the config for this plugin may confirm (or refute) this theory. My guess is before making a change the protocol setting won't be there at all, and any change will get it filled in and fix the issue.

@recrudesce
Copy link

No amount of changing anything fixed this for me. I even uninstalled and reinstalled the plugin. It would show the alert icon, which would disappear, but then the button would do nothing at all - the state of the blocking always remained enabled in my Pihole.

Shame, cos it was quite useful.

@gbutts
Copy link

gbutts commented Oct 9, 2023

I am seeing the same issue.

Could this be related to the situation where (after a recent Pi-hole update) simply typing the IP address into a browser returns a '403 Forbidden'?

To get Pi-hole to open in a browser now you have to use 'http://ip/admin'

See: https://pi-hole.net/blog/2023/01/15/pi-hole-ftl-v5-20-1-web-v5-18-1-and-core-v5-15-released/#page-content

@Webranger2
Copy link

I am seeing the same issue.

Is there already a solution?

I can only open my pihole via http://IP/admin/

@benjisoft
Copy link

I was also experiencing this issue. By removing http:// from before the IP it worked for me

@s1nfin
Copy link

s1nfin commented Mar 15, 2024

For me neither IP Address nor Hostname worked....

But for me it worked to just use "pi.hole:8081"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants