Adam Warner

It looks like there are two separate issues being discussed in this thread. To keep things tidy - the `no such table` warnings are being looked at here : https://github.com/pi-hole/AdminLTE/issues/2117...

Is this still an issue in the latest tag?

> How often do you make new releases or is pihole/pihole:latest just the tip of the master branch? Generally they're in line with releases in the non-container repos (https://github.com/pi-hole/pi-hole, https://github.com/pi-hole/adminLTE,...

Edit the file at `/etc/dnsmasq.d/05-pihole-custom-cname.conf` and remove the offending line.

Ah! That's where I put it. I knew I'd typed it.... 😄 Yes, meant for a different issue.

Seems like there are some solutions in this issue thread. PRs are welcome - we don't bite too hard

> if the CAP_NET_BROADCAST is required or NET_ADMIN is enough NET_ADMIN should be enough here. Pull requests are welcome with any improvements to the docs, though I do agree they...

~Huh, I could have sworn we patched that out of the Docker images... has it crept back in somewhere?~ My mistake, looks like it was just the update and help...

Can confirm this behaviour still exists on latest `:dev` container. Though it is just cosmetic: ``` pi@dockerpi:~ $ docker exec -it pihole pihole status [✓] FTL is listening on port...

TL;DR - you can safely unbind port 443. There is nothing _inside_ the container listening on that port It harks back to a time when the default [blocking mode ](https://docs.pi-hole.net/ftldns/blockingmode/)...