-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Failed Host Check #280
Comments
Noticed a potential fix on Discourse: https://discourse.pi-hole.net/t/add-support-for-port-80/912. Would be a great fix for me. I would simply change admin port to 8090 to have it mirror the external one. But the "auth.php" file is no more, as I can see.
|
Great!!!
Il giorno gio 22 dic 2016 alle 13:05 DL6ER <[email protected]> ha
scritto:
You should have done some more investigations on this topic - I fixed that
already yesterday!
See Pull Request #279 <#279> as
well as also the issue #279 <#279>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAItKg7WJwF1ejfDN9zD_r1u4j7H2sX7ks5rKmdugaJpZM4LTzpW>
.
--
Stefano Valicchia - Giardiniere Informatico
|
This issue has been mentioned on Pi-hole Userspace. There might be relevant details there: https://discourse.pi-hole.net/t/brought-back-and-old-error/50175/1 |
Hi! Thanks again for the PiHole (and new features) but now I'm having an issue connecting to the web interface from a remote location:
When I try to connect through my router "domain" (I have an Asus with a DynDns kind of external hostname service) the new interface doesn't match the domain (it only has a different port) For example if i try to connect to xxxxxxx.asuscomm.com:8090/admin (real subdomain is redacted for security reason) it gives you a "Failed Host Check" as it has whitelisted xxxxxxx.asuscomm.com (no port here). I can't change forwarded port (80 is in use).
The error message is as such:
Failed Host Check: xxxxxxx.asuscomm.com:8090 vs http://192.168.1.166, http://xxxxxxx.asuscomm.com, http://pi.hole, http://localhost
Expected Behaviour:
Remotely connect through a remote port forwarded dynamic ip hostname.
Actual Behaviour:
Failed Host Check... No Joy!
Steps to reproduce this issue:
Create DynDns domain to your PiHole device through not-80 port forwarding on your router and try to connect to your PiHole admin interface.
Thanks again.
The text was updated successfully, but these errors were encountered: