1. Output of caddy version:
v2.6.2 h1:wKoFIxpmOJLGl3QXoo6PNbYvGW4xLEgo32GPBEjWL8o=
2. How I run Caddy:
Docker-compose
a. System environment:
Docker
b. Command:
docker-compose up -d
Paste command here.
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane. →
version: "2.1"
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 lookatme33@protonmail.com
# Optional staging lets encrypt for testing. Comment out for production.
# acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
}
matrix.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
}
matrix.naff.casa {
reverse_proxy 192.168.1.37:8008
}
element.naff.casa {
reverse_proxy 192.168.1.37:8089
}
Paste your config here, replacing this text.
Use `caddy fmt` to make it readable.
DO NOT REDACT anything except credentials.
LEAVE DOMAIN NAMES INTACT.
Make sure the backticks stay on their own lines.
3. The problem I’m having:
Caddy worked great with Matrix previously and I’m not sure if there’s been an upgrade to Caddy or an upgrade to Matrix becuase my instance no longer works and isn’t federated (fails federation checker).
4. Error messages and/or full log output:
Paste logs/commands/output here.
USE THE PREVIEW PANE TO MAKE SURE IT LOOKS NICELY FORMATTED.
5. What I already tried:
I tried re-creating my instance with an new post-gres database – thought that was the issue but it still won’t federate.
