Docker compose: moving to a new domain

I tried to move squidex to a new domain, but can’t get it to load again due to SSL errors.
I changed the SQUIDEX_DOMAIN, didn’t work out of the box. Tried to delete the volumes of the caddy-proxy but still no luck. Tried to find a squidex help or community entry, but no luck.

Any idea how to make this work? Thx

Have you checked the caddy logs? What exactly “did not work”?

2023/03/17 13:45:55 http: TLS handshake error from x.x.x.x:59622: no certificate available for ‘xxxx.xxxxxxx.de

Where is this log from?

its from “docker logs” and the caddy container

2023/03/18 08:47:53 [ERROR] Making new ACME client: get directory at 'https://acme-staging-v02.api.letsencrypt.org/directory': Get "https://acme-staging-v02.api.letsencrypt.org/directory": context deadline exceeded (Client.Timeout exceeded while awaiting headers) (attempt 1/2)
2023/03/18 08:48:25 [ERROR] Making new ACME client: get directory at 'https://acme-staging-v02.api.letsencrypt.org/directory': Get "https://acme-staging-v02.api.letsencrypt.org/directory": context deadline exceeded (Client.Timeout exceeded while awaiting headers) (attempt 2/2)
2023/03/18 08:48:25 [ERROR] attempt 15: [xxxxx.de] Obtain: get directory at 'https://acme-staging-v02.api.letsencrypt.org/directory': Get "https://acme-staging-v02.api.letsencrypt.org/directory": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 6h0m0s (24h15m30.595804067s/720h0m0s elapsed)...
2023/03/18 09:29:43 http: TLS handshake error from 128.14.134.170:50798: no certificate available for '172.19.0.4'
2023/03/18 09:45:23 http: TLS handshake error from 3.131.98.176:37770: no certificate available for 'xxxxx.de'
2023/03/18 09:45:24 http: TLS handshake error from 3.131.98.176:37780: no certificate available for 'xxxxx.de'
2023/03/18 09:45:24 http: TLS handshake error from 3.131.98.176:37792: no certificate available for 'xxxxx.de'

Perhaps canny cannot talk with letsencrypt? I have no idea what the root cause is.