Woke up with a broken Caddy

1. Output of caddy version:

latest

2. How I run Caddy:

Docker

a. System environment:

UBUNTU/VM/PROXMOX

b. Command:

Paste command here.

c. Service/unit/compose file:

services:
        caddy:
                container_name: caddy
                image: caddy:latest
                restart: unless-stopped
                ports:
                        - "80:80"
                        - "443:443"
                volumes:
                        - /docker/caddy/Caddyfile:/etc/caddy/Caddyfile
                        - /docker/caddy/data:/data
                        - /docker/caddy/srv:/srv
                        - /docker/caddy/config:/config
                networks:
                        - t2_proxy
networks:
  t2_proxy:
    external: true

d. My complete Caddy config:

{
        # Global options block. Entirely optional, https is on by default
        # Optional email key for lets encrypt
        email ryan@naff.casa
        # Optional staging lets encrypt for testing. Comment out for production.
        #     acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
}
naff.casa {
        # enable logging
        log

        # .well-known is delegated from example.co.uk and served here
        header /.well-known/matrix/server {
                Content-Type application/json
        }
        respond /.well-known/matrix/server 200 {
                body "{ \"m.server\": \"matrix.naff.casa:443\" }"
                close
        }
        # .well-known delegate for client
        header /.well-known/matrix/client {
                Content-Type application/json
        }
        respond /.well-known/matrix/client 200 {
                body "{\"m.homeserver\": {\"base_url\": \"https://matrix.naff.casa\"}}"
                close
        }

        reverse_proxy /_matrix/* http://192.168.1.37:8008
        reverse_proxy /_synapse/client/* http://192.168.1.37:8008
    reverse_proxy 192.168.1.37:2368
}
recipes.naff.casa {
        reverse_proxy 192.168.1.37:8081
}
share.naff.casa {
        reverse_proxy 192.168.1.37:7070
}
logs.naff.casa {
        reverse_proxy 192.168.1.37:9999
}
bin.naff.casa {
        reverse_proxy 192.168.1.37:6608
}
paste.naff.casa {
        reverse_proxy 192.168.1.37:8085
}
remote.naff.casa {
        redir / /guacamole
        reverse_proxy 192.168.1.37:6969
}
books.naff.casa {
        reverse_proxy 192.168.1.37:5006
}
port.naff.casa {
        reverse_proxy 192.168.1.37:9000
}
www.naff.casa {
        redir https://naff.casa{uri}
}
sonarr.naff.casa {
        reverse_proxy 192.168.1.36:8989
}
radarr.naff.casa {
        reverse_proxy 192.168.1.36:7878
}
ombi.naff.casa {
        reverse_proxy 192.168.1.36:3579
}
bw.naff.casa {
        reverse_proxy 192.168.1.37:8711
}
cctv.naff.casa {
        reverse_proxy 192.168.1.224:8123
}
jellyfin.naff.casa {
        reverse_proxy 192.168.1.36:8096
}
code.naff.casa {
        reverse_proxy 192.168.1.37:4443
}
matrix.naff.casa {
        reverse_proxy 192.168.1.37:8008
}
element.naff.casa {
        reverse_proxy 192.168.1.37:8089
}
prox.naff.casa {
        reverse_proxy 192.168.1.218:8006 {
                transport http {
                        tls_insecure_skip_verify
                }
        }
}
www.social.naff.casa {
    redir https://social.naff.casa{uri}
}
social.naff.casa {
    encode zstd gzip
    reverse_proxy /api/v1/streaming* 192.168.1.216:4000
    reverse_proxy 192.168.1.216:3000
}

3. The problem I’m having:

4. Error messages and/or full log output:

Can you clarify what broken means? How do you know it’s broken? What’s in your logs? Which domain has the problem? Please fill out the template in full so know how to help you

I’ve posted my logs – for some reason it’s now showing on here.

By broken, I mean, all of my services are not working – I have over 13 services being redirected.
I’m not sure why my logs aren’t showing as well as the rest of my post, when I edit this post, I can see it all.

Solved via Discord.

The WAN IP changed, DDNS tool didn’t update it.

2 Likes