Help! Docker caddy suddenly no longer can find DNS records?

Ayyy you got nextcloud working again!! Nice job!! YESSS!!! I was sooo close to giving up. Thank you!! I figured out jellyfin’s problem (it was me so you can skip the below trouble shooting). Here’s what was happening:


When I had tailscale working by itself it was not necessary to hit in a server.
Here’s a list of other IP’s I’ve tried:

https://jellyfin.wallaby-gopher.ts.net:8096
https://jellyfin.wallaby-gopher.ts.net:8920
172.18.0.3
172.18.0.3:8096
https://172.18.0.3
100.102.29.56
100.102.29.56:8096
https://100.102.29.56

Looking back at the guide they threw this in the caddy file:

127.0.0.1 {
	reverse_proxy jellyfin:8096
}

Looking at the jellyfin logs I’m like, maybe I need to do the same even though in portainer it’s labeled as 172.18.0.3

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN subnets: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions: []

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Used LAN subnets: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered interface addresses: ["127.0.0.1", "172.18.0.3"]

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["0.0.0.0"]

[01:47:26] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Remote IP filter is Allowlist

All it adds in a warning in caddy though and the same server add page

WRN ts=1722563249.706316 logger=tls msg=stapling OCSP error=no OCSP stapling for [127.0.0.1]: no OCSP server specified in certificate identifiers=["127.0.0.1"]

So I thought I’d try the same thing as nextcloud

ERR ts=1722563572.2223425 logger=http.log.error msg=dial tcp 172.17.0.1:8096: connect: connection refused request={"remote_ip":"100.122.199.7","remote_port":"60034","client_ip":"100.122.199.7","proto":"HTTP/2.0","method":"GET","host":"jellyfin.wallaby-gopher.ts.net","uri":"/web/serviceworker.js","headers":{"Dnt":["1"],"Sec-Fetch-Mode":["same-origin"],"Te":["trailers"],"User-Agent":["Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0"],"Accept":["*/*"],"Service-Worker":["script"],"Sec-Gpc":["1"],"Sec-Fetch-Dest":["serviceworker"],"Sec-Fetch-Site":["same-origin"],"Priority":["u=4"],"Cache-Control":["max-age=0"],"Accept-Language":["en-US,en;q=0.5"],"Accept-Encoding":["gzip, deflate, br, zstd"]},"tls":{"resumed":false,"version":772,"cipher_suite":4865,"proto":"h2","server_name":"jellyfin.wallaby-gopher.ts.net"}} duration=0.00020961 status=502 err_id=6zn8cs5ru err_trace=reverseproxy.statusError (reverseproxy.go:1269)

Interesting that NONE of the containers have that IP


I saw this post saying you need to clear the cache, no dice.
Turns out, it was the damn local paths to configs again. I moved it into a volume and it immediately started working.

Oh heavens no, I think it’s neat you formatted it into one file like that!!
Okay, I removed that line.

1 Like