Dns stopped working randomly. Seams pi has not internet access anymore, FTL log being spammed

[Liquidmasl]

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

Expected Behaviour:

Pihole should continue to work like it did the past weeks

Actual Behaviour:

Randomly at 10:05 no homepage was accessible anymore. DHCP also stopped working

Debug Token:

Cant provide currently because the pihole seams to have lost connection to the internet so i cant upload it but can post it in text here

Nothing changed this morning, we had a short blackout yesterday, but after that everything worked fine.

I changed nothing really.
Pihole is running in proxmox, a static ip is set and the default gateaway aswell

Although when checking my rounter, I do not see the .99 ip as a connected device.

After manually assigning my pc a static ip so i could even access the pihole i saw:

The FTL log is being absolutly spammed (as can be seen in de debug log at the bottom)
I cant even look at the long time logs because i get a PHP memory error.

Also in the debug log it seams the default gateaway is not set. but it is set in the DHCP settings.

Again to reiterate, i changed nothing on the configuration. It just stopped working at 10:05, as can be seen on the graph

For now i will have to disable the pihole and go back to my routers DHCP.
Can someone help me out here?
I am WAY out of my waters here. I am an IT guy, but Network stuff is something i always somewhat avoided :\

Thanks in advance!

Moderator edit: explicit debug log removed

[Bucking_Horn]

(For your own privacy and security, please do not post the full, unsanitised output here.)

@Liquidmasl

*** [ DIAGNOSING ]: Ports in use
[✓] tcp:0.0.0.0:80 is in use by lighttpd
    tcp:127.0.0.1:25 is in use by master
    tcp:*:22 is in use by sshd
[✓] tcp:[::]:80 is in use by lighttpd
    tcp:[::1]:25 is in use by master

Above output indicates that Pi-hole's DNS/DHCP server pihole-FTL wasn't active when that check was performed, or perhaps the check may lack necessary privileges to see those ports in your virtualized environment.

(Edit: The former may happen if port 53 and/or 67 would have been already occupied when Pi-hole tried to bind them, preventing pihole-FTL to start successfully.)

The latter may be possible, as your debug log also shows pihole-FTL to have been active, e.g.:

@Liquidmasl

*** [ DIAGNOSING ]: Pi-hole log
-rw-r----- 1 pihole pihole 1.5G Jul 31 08:59 /var/log/pihole/pihole.log
   -----head of pihole.log------
   Jul 31 00:00:09 dnsmasq[221]: config error is REFUSED (EDE: network error)
   Jul 31 00:00:09 dnsmasq[221]: query[A] pool.ntp.org from 192.168.0.233
   Jul 31 00:00:09 dnsmasq[221]: config error is REFUSED (EDE: network error)

That REFUSED would suggest that Pi-hole wasn't aware of any functional upstream DNS servers, or all of Pi-hole's configured upstreams have been inaccessible at the logged time.

You should verify that your router's firewall does not block your Pi-hole host device, and that your virtualisation environment provides outbound network connectivity for Pi-hole.

[Liquidmasl]

if I undersrand correctly, the pihole host device is my proxmox server, which is reachable just fine, and shows up in my connected devices. Same is true for my homeassistant server that is running on the proxmox machine aswell.

everything else you said would make sense if the pihole just has no connection to the internet. But why did it lose connection randomly?

Possibly not piholes fault as it seams?