Pihole chronometer connection refused

Help Community Help
25 
sudo rm /var/run/pihole-FTL.port
echo 8083 | sudo tee /var/run/pihole-FTL.port

or change back the FTLPORT

27

I can't open the debug log, but does pihole -c work now?

28

Looks like FTL is still on that port:

127.0.0.1:8083 pihole-FTL (IPv4)

29

Is this not ok?

30

SharedScreenshot
SharedScreenshot988×410 44.4 KB

33

Just use port 4711, the default, and stop screwing with it.

1 Like
34

I had only done what was written to me.

35

Where was it written that you should change the port?

36

Here.

37

I meant: where was it written in the first place?

39

Thanks for everything and your time. It works. Was a little blind.

But:

SharedScreenshot
SharedScreenshot988×410 44.4 KB

40

Does sudo cat /var/run/pihole-FTL.port match the port?

[53] is in use by pihole-FTL
[53] is in use by pihole-FTL
[4711] is in use by pihole-FTL
[4711] is in use by pihole-FTL
42

Then that's why it doesn't work.

Sorry to be curt but you're running a DNS server and from the looks of your log you have the web interface publicly accessible with a FQDN. You need to have a basic level of knowledge of what you are doing and why you are doing it. You have all the information you need to solve this issue, you need to fix it yourself.

43

The dashboard finally shows everything, only FTL is missing now. PI-Hole hadn't had any problems before. Only since the update to 5.1.1.

/var/run/pihole-FTL.port

MAXLOGAGE=24.0
FTLPORT=4711
PRIVACYLEVEL=0

44

Try running pihole -r , choose "repair" to reset your installation.

45

no change

47

Now you have FTL back on port 4711. Run the following:

echo 4711 | sudo tee /var/run/pihole-FTL.port

48

I do not understand anything anymore. Everything done like this and suddenly everything works.

50

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