1. Caddy version (caddy version):
2. How I run Caddy:
a. System environment:
b. Command:
docker-compose up -d
c. Service/unit/compose file:
version: "2.4"
services:
caddy:
image: caddy:2.4.6
container_name: caddy
restart: always
environment:
ACME_AGREE: "true"
ports:
- 9934:9934
- 9945:9945
- 80:80
- 443:443
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- ./caddy:/root/.caddy
d. My complete Caddyfile or JSON config:
{
acme_ca https://acme-v02.api.letsencrypt.org/directory
}
abc.xyz.com:9945 { #WebSocket
reverse_proxy / docker_node:9944
}
abc.xyz.com:9934 { #HTTP
reverse_proxy / docker_node:9933
}.
3. The problem I’m having:
After couple of days, Caddy stop working and required restarts. But in the next few days, problem happen again.
4. Error messages and/or full log output:
{“level”:“error”,“ts”:1648719023.5534458,“logger”:“http.log.error”,“msg”:“read tcp 172.18.0.3:33724->172.18.0.2:9944: read: connection reset by peer”,“request”:{“remote_addr”:“54.203.31.176:41776”,“proto”:“HTTP/1.1”,“method”:“GET”,“host”:“archive.mainnet.sample.com:9945”,“uri”:"/",“headers”:{“Upgrade”:[“websocket”],“Connection”:[“Upgrade”],“Sec-Websocket-Version”:[“13”],“Sec-Websocket-Key”:[“SVsvz0mpUIYli+n1XkK9dQ==”]},“tls”:{“resumed”:false,“version”:772,“cipher_suite”:4865,“proto”:"",“proto_mutual”:true,“server_name”:“archive.mainnet.sample.com”}},“duration”:0.002754093,“status”:502,“err_id”:“n9br3pkdz”,“err_trace”:“reverseproxy.statusError (reverseproxy.go:886)”}
5. What I already tried:
Just restart