pi-hole/web

Web interface not accessible after container restart until the lists in the background are downloaded

LizenzFass78851 opened this issue · 0 comments

LizenzFass78851 commented

Versions

  • Pi-hole: development-v6 ed5d794
  • web: development-v6 a2567bf
  • FTL: development-v6 vDev-baea4a8

Platform

  • OS and version: Ubuntu 22.04 amd64
  • Platform: Docker (using docker compose)

Expected behavior

When you restart the pihole container, the web interface should be accessible immediately, as is the case with v5. Even if it reloads or synchronizes the block lists in the background after restarting the container.

Actual behavior / bug

When the Pihole container restarts, it downloads the lists in the background, which is not the problem, but while Pihole is doing this, the web interface is not reachable (and apparently the pihole as a DNS server is also not reachable)

Steps to reproduce

Steps to reproduce the behavior:

  1. I go to the Lists menu item
  2. I remove the default list from stevenblocks
  3. I add a large collection of blocklists from @RPiList
  4. I go to the console and download the lists with pihole -g. (Meanwhile, the web interface is still accessible during and after the list update)
  5. I stop and restart the pihole container with the commands docker-compose down && docker-compose up -d.
  6. in docker logs (container name) you can see that it is comparing the lists again (and from then on the web interface is not accessible and DNS queries don't work either until the download or the comparison for the lists in the background is finished.)

Debug Token

Screenshots

Additional context

It may be a strange error, but I would like to mention it because in pihole version 5 it worked as I described above.
It would be bad if someone entered a lot of block lists, which also helps protect the internet and the pihole in v6 can no longer work properly with large lists or the reactions described above occur.