Updating pihole causes problems (Ubuntu 20.04)

##Expected Behaviour:
Pihole should have updated normally

Actual Behaviour:

I encountered an issue when updating

I get this which I have never gotten in the past:

  [✗] Retrieval of supported OS list failed. dig failed with return code 10.
      Unable to determine if the detected OS (Ubuntu 20.04) is supported

Then I read about skipping OS check and the update still fails here:

[✗] Downloading and Installing FTL
  Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-linux-x86_64 not found
  [✗] FTL Engine not installed

Debug Token:

It could not upload the log, so no token...

[?] Would you like to upload the log? [y/N] y
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

[✗]  There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole_debug.log

Set a different nameserver in /etc/resolv.conf (e.g. 8.8.8.8) and try again.

Good grief do I feel stupid.... do I need to change the resolv.conf back? it was 127.0.0.53... or should I leave it to a public nameserver?

Content in the /etc/resolv.conf file will be restored to how it was before on reboot or network state change.
But that 127.0.0.53 ip being there originaly would indicate a stub resolver running that could conflict with pihole-FTL.
What does below one show?

sudo ss -nltup sport = 53

EDIT: Ow and after changing the nameserver in resolv.conf, try run the debugger: pihole -d
, upload the logs and post only the resulting token here?

Sorry for delay... My ISP went down for a day after reading this.

I have run the debug. I also have seen some odd messages in the diagnosis.

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

diagnosis errors below... Nothing else is configured for 252, and it is NOT in my DHCP range. also my DHCP range has more than enough addresses for my clients.

Any thoughts would be helpful, but at this point I am somewhat considering blowing up my install and spinning up a new VM with dietpi or anything else that might be recommended here.

Pi-hole diagnosis:
2022-08-07 04:13:40 DNSMASQ_WARN Warning in dnsmasq core:

Maximum number of concurrent DNS queries reached (max: 150)

Check out our documentation for further information.
2022-08-07 10:55:28 DNSMASQ_WARN Warning in dnsmasq core:

no address range available for DHCP request via lo

Check out our documentation for further information.
2022-08-07 10:55:28 DNSMASQ_WARN Warning in dnsmasq core:

not using configured address 192.168.50.252 because it is in use by the server or relay

Check out our documentation for further information.
2022-08-07 10:58:02 DNSMASQ_WARN Warning in dnsmasq core:

no address range available for DHCP request via lo

Check out our documentation for further information.
2022-08-07 10:58:02 DNSMASQ_WARN Warning in dnsmasq core:

not using configured address 192.168.50.252 because it is in use by the server or relay

Check out our documentation for further information.
2022-08-07 12:01:24 DNSMASQ_WARN Warning in dnsmasq core:

Maximum number of concurrent DNS queries reached (max: 150)

Check out our documentation for further information.
2022-08-07 12:01:31 DNSMASQ_WARN Warning in dnsmasq core:

Maximum number of concurrent DNS queries reached (max: 150)

Thanks!

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