Caddy uses wrong local DNS IP?

Help
1

1. Caddy version:

v2.6.2
slothcroissant/caddy-cloudflaredns

2. How I installed, and run Caddy:

Caddy 2 is installed via docker-compose

a. System environment:

Summary

Client: Docker Engine - Community
Version: 20.10.23
API version: 1.41
Go version: go1.18.10
Git commit: 7155243
Built: Thu Jan 19 17:34:13 2023
OS/Arch: linux/amd64
Context: default
Experimental: true

Server: Docker Engine - Community
Engine:
Version: 20.10.23
API version: 1.41 (minimum version 1.12)
Go version: go1.18.10
Git commit: 6051f14
Built: Thu Jan 19 17:32:04 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.15
GitCommit: 5b842e528e99d4d4c1686467debf2bd4b88ecd86
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0

3. The problem I’m having:

Everythig was working like a charm for days and even until yesterday before I went to sleep. Then I woke up and my site was down.

The problem I think I’m having is that caddy wants to do something with 127.0.0.11 when it probably needs 127.0.0.1. How do I fix this? I looked in the folders from my volumes but I can’t find anything there.

4. Error messages and/or full log output:

See 6

5. What I already tried:

Forwarded Port 53 in my router udp/tcp
Whitelisted zerossl, letsencrypt and my domain in the pihole
Removed caddy volumes
Recreated pihole
Checked if the custom resolve.conf mounted in my pihole is leading to a wrong dns
Checked if I get an IP on other containers in another network which I do get

6. Links to relevant resources:

https://paste.debian.net/hidden/f1d26f52/

2

127.0.0.11 is typically the IP address of the Docker DNS resolver.

This isn’t a Caddy question, really. Something is weird with your Docker or system setup.

Also, remember that 127.0.0.1 within a container is trying to connect to itself, which usually will not work, because containers there won’t be any other program to connect to in there.

1 Like
3

Thanks for your fast answer again francis!

Well seems like it will be a stressful weekend. :sob:

4

Actually found the solution now!

I moved my setup to another machine yesterday.
After fiddling around and even restoring a snapshot from yesterday evening I finally ended up looking at my network configuration and saw that the field for the mac adress is empty. So I chose the correct one from my network adapter, restarted everything and it’s working again. :slight_smile:

1 Like
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.