Disabling Pi-Hole doesn't disable it

[argeljoseph]

This is a: BUG

Details

In my a docker environment, even though the Pi-Hole is supposed to be disabled (in the attachment, chosen indefinitely) I then try to access sites that are blocked by Pi-Hole, and they are still blocked. I then try and click on settings (or you can try any other link within Pi-Hole), and somehow Pi-Hole is in enabled state.

Related Issues

• [*] I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

1. Environment data

• Operating System: (Not sure as using docker image)
• Hardware: QNAP TS-264
• Kernel Architecture:
• Docker Install Info and version:
  • Software source: docker
  • Supplimentary Software: n/a
• Hardware architecture:

2. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
3. any additional info to help reproduce

These common fixes didn't work for my issue

• [*] I have tried removing/destroying my container, and re-creating a new container
• [*] I have tried fresh volume data by backing up and moving/removing the old volume data
• [*] I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
• [*] I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
• [*] I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

[rdwebdesign]

2. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here

Please:

1. post your compose file (or docker run command) used to start your container.
2. Generate and upload a debug log, then post here only the Token.