pi-hole / docker-pi-hole

Pi-hole in a docker container
https://pi-hole.net
Other
8.46k stars 1.13k forks source link

"DataTables warning: table id=all-queries" after pulling the latest image #225

Closed unixfox closed 6 years ago

unixfox commented 6 years ago

I've upgraded my docker-pi-hole to the latest image using:

docker-compose stop
docker-compose rm -f
docker-compose pull   
docker-compose up -d

When I browse to the "Query log" section I get this error:

DataTables warning: table id=all-queries - Requested unknown parameter '5' for row 0, column 5. For more information about this error, please see http://datatables.net/tn/4

I tried to increase the limit of php with theses two values: https://github.com/pi-hole/AdminLTE/pull/308/files but that solve nothing.

diginc commented 6 years ago

Have you tried moving any existing volume data to the side and starting fresh?

unixfox commented 6 years ago

You mean reinstalling and erase my existing volume? If I do that I will lost my existing settings (blocklists, whitelist and blacklist). By the way I'm forgot to tell you that I'm using the debian_dev branch.

diginc commented 6 years ago

You don't need to delete your existing volumes on the off chance it's not the data in them causing the problem. I'd suggest just moving them to the side and re-creating the container again so it creates an empty volume directory.

unixfox commented 6 years ago

I tried your solution but it didn't fix the issue, here is what I did:

docker-compose stop
docker-compose rm -f
mv etc etc.back
docker-compose pull
docker-compose up -d
diginc commented 6 years ago

What does your docker-compose.yml look like?

is your volume ./etc/:/etc/ ? Try without that.

unixfox commented 6 years ago

Here is my docker-compose.yml:

version: "2"
services:
  pihole:
    image: diginc/pi-hole:debian_dev
    dns:
    - 127.0.0.1
    - 9.9.9.9
    ports:
      #- "53:53/tcp"
      #- "53:53/udp"
      - "8080:80/tcp"
    environment:
      - ServerIP=x.x.x.x
      - VIRTUAL_HOST=pihole.example.com
      - DNS1=139.59.208.246
      - DNS2=9.9.9.9
      - DNS=127.0.0.1
      - IPv6="False"
      - TZ=Europe/Brussels
      - DNSMASQ_LISTENING=all
      - WEBPASSWORD=passwd
    volumes:
      - '/root/pihole/etc/:/etc/pihole/'
      - '/root/pihole/dnsmasq.d/:/etc/dnsmasq.d/'
    networks:
      dns:
        ipv4_address: 172.23.1.254
        aliases:
          - pihole
    restart: always
  wrapper:
    image: vimagick/dnscrypt-wrapper
    ports:
      - "4443:443/udp"
      - "4443:443/tcp"
    dns:
        - 172.23.1.254
    volumes:
      - '/root/pihole/dnscrypt/:/var/lib/dnscrypt-wrapper'
    environment:
      - LISTEN_ADDR=0.0.0.0:443
      - RESOLVER_ADDR=172.23.1.254:53
      - PROVIDER_NAME=2.dnscrypt-cert.unixfox.eu
    depends_on:
      - pihole
    networks:
      dns:
        aliases:
          - dnscrypt
    restart: always

networks:
  dns:
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 172.23.1.0/24
unixfox commented 6 years ago

I removed the entry for the volume of pihole but I still get the same issue.

diginc commented 6 years ago

hmm you seem to be doing everything right. Your port setup reminds me of #224 which was custom ports causing issues. I've never seen that before my self but maybe this is a new problem.

If returning to default ports doesn't help then perhaps there is a hint somewhere in docker-compose logs or docker-compose exec pihole debug

unixfox commented 6 years ago

Here is the logs of docker-compose logs: https://hastebin.com/iviterayej.log and pihole debug: https://hastebin.com/inenoxoxaq.log (debug token for devs of pihole: 189vcxksnb).

I tried to bind on the default ports but that doesn't solve the issue.

I don't see any error related to my issue, that's strange.

unixfox commented 6 years ago

I've a strange other issue too, when I updated the list the progress was shown, now it's stuck until the process has finished: selection_267

I was thinking that my issue could be an upstream issue and pulling the latest changes from the repository of pihole could resolve my issue?

diginc commented 6 years ago

Turns out FTL was out of date and the latest dev pihole/web were incompatible with the older FTL.

227 addressed this hopefully. A new image is building now.

unixfox commented 6 years ago

Thank you for the update @diginc. I tried the new image and I got a new bug, nothing is logged:

selection_271

unixfox commented 6 years ago

I've reseted my volume and now it's working fine. Thank you.