Caddy can't download directory from acme because of ipv6

(Mateusz Iwaniszczuk) #1

Hello, when I try to start caddy it tries to get json from but it fails because it tries to use ipv6 to connect to that site. I use Arch Linux
My Caddyfile
`(wildcard_cert) {
tls {
dns cloudflare
} {
root /srv/http/
log /srv/http/
errors /srv/http/
Jan 01 14:04:24 ivan systemd[1]: Started Caddy HTTP/2 web server. Jan 01 14:04:24 ivan caddy[537]: Activating privacy features... 2019/01/01 14:04:24 making ACME client to get ToS URL: get directory at '': failed to get json "": Get dial tcp: lookup on [::1]:53:read udp [::1]:38193->[::1]:53: read: connection refused Jan 01 14:04:24 ivan systemd[1]: caddy.service: Main process exited, code=exited, status=1/FAILURE Jan 01 14:04:24 ivan systemd[1]: caddy.service: Failed with result 'exit-code'.
On server there is ipv6 interface but without internet access so I tried to disable it but same result with small change in error log connect: cannot assign requested address instead of read: connection refused.
I tried do ipv6 tunneling and it works because I can ping via ipv6

but same error with read: connection refused on caddy web server :frowning: How I can force caddy to use ipv4 or to connect by ipv6 properly?
I start caddy by systemd service

Description=Caddy HTTP/2 web server
Documentation= systemd-networkd-wait-online.service


; User and group the process will run as.

; Letsencrypt-issued certificates will be written to this directory.

; Always set “-root” to something safe in case it gets forgotten in the Caddyfile.
ExecStart=/usr/local/bin/caddy -log stdout -agree=true -quic -conf=/etc/caddy/Caddyfile -root=/var/tmp
ExecReload=/bin/kill -USR1 $MAINPID

; Use graceful shutdown with a reasonable timeout

; Limit the number of file descriptors; see man systemd.exec for more limit settings.
; Unmodified caddy is not expected to use more than that.

; Use private /tmp and /var/tmp, which are discarded after caddy stops.
; Use a minimal /dev (May bring additional security if switched to ‘true’, but it may not work on Raspberry Pi’s or other devices, so it has been disabled in this dist.)
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
; Make /usr, /boot, /etc and possibly some more folders read-only.
; … except /etc/ssl/caddy, because we want Letsencrypt-certificates there.
; This merely retains r/w access rights, it does not add any new. Must still be writable on the host!

; The following additional security directives only work with systemd v229 or later.
; They further restrict privileges that can be gained by caddy. Uncomment if you like.
; Note that you may have to add capabilities required by any plugins in use.


(Matthew Fay) #2

Hi @MrVanosh, welcome to the Caddy community.

Just to clarify, it is networked (interface is up), but without internet access?

Did you bring down the interface, or did you disable IPv6 globally?