DNS issues and unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47

Help
1

Please follow the below template, it will help us to help you!

Hi All,

Expected Behaviour:

_[Replace this text with what you think should be happening. Please include as much detail as possible including, but not limited to:

This is a standard install running on Raspberry Pi
PI400-4GB
4GB RAM LPDDR-32000
16GB SD Card with Raspbian OS

Pi-hole version is v5.17.1 (Latest: v5.17.1)
AdminLTE version is v5.20.1 (Latest: v5.20.1)
FTL version is v5.23 (Latest: v5.23)

NOTE: Upstream DNS server is a single Adguard IP (IPv4).

  • The home router 192.168.1.1 serves DHCP and has itself as the DNS server in the distribution.
  • I also deleted and recreated the (large) FTL.db
  • Not using Conditional Forwarding in the DNS settings page.
  • Rate limiting is not enabled.

Actual Behaviour:

The FTL and DNS services have been failing/hanging since the past few weeks and I couldn't find a resolution from the past threads about this topic, so creating a new one.
Currently the Web UI shows that the DNS service is not running and the settings page shows the error:
"PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47"
Please advise next steps to troubleshoot.
Thanks for all the help!

Debug Token:

https://tricorder.pi-hole.net/M6tbJF1v/

2

This one slipped past us - apologies.

Did you manage to solve your issue in the meantime?

If not, please provide a fresh debug token (your previous one has expired).

3

Hello,
Thank you for getting back.
Yes, the issue resolved by:

  1. Full update of the OS and packages (some fail but that's not impacting Pihole).
  2. Removing Pihole DNS IP address from the outside "WAN" interface of the Ubiquiti Unifi UXG-Pro router. All internal (LAN) networks hand out the Pihole-DNS IP using DHCP, but we had the WAN interface also pointing to it in its DNS config.
    Guess the WAN interface was jumping into the inside network and creating some sort of a loop?
    We have since left the WAN DNS IP to Ad-Guard/OpenDNS/Quad9.
4

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.