Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caddy example: DNS-over-TLS? #1673

Open
1 of 6 tasks
Noriller opened this issue Dec 21, 2024 · 1 comment
Open
1 of 6 tasks

Caddy example: DNS-over-TLS? #1673

Noriller opened this issue Dec 21, 2024 · 1 comment

Comments

@Noriller
Copy link

This is a: Documentation Issue

Details

In the caddy example:

https://github.com/pi-hole/docker-pi-hole/blob/master/examples/docker-compose-caddy-proxy.yml

It has this line:

      - "853:853/tcp" # DNS-over-TLS 

Which leads to believe you might serve it as secure DNS, but from what I've seem from the rest of the docs it doesn't seem to be the case.

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: ENTER HERE
  • Hardware:
  • Kernel Architecture:
  • Docker Install Info and version:
    • Software source:
    • Supplimentary Software:
  • Hardware architecture:
  1. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
  2. 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.

@yubiuser
Copy link
Member

Thanks.
This line should be removed.
Fixed by #1674

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants