1. The problem I’m having:
I am using caddy for reverse proxy on my node app, and recently it has been crashing (like the service) I’m not sure why. I get 80k users daily on my website and when it crashes the links I put in the Caddyfile go up after the restart but the Auto TLS/SSL links I set up take a long time to go up. (i have over 1k links pointing to my node app) I don’t know why this happens, can anyone help?
2. Error messages and/or full log output:
there isnt a specific error, it just tells me that the service is inactive and that it was killed when i do systemctl status caddy
after it crashed. there are http reverse proxy errors, but i think that is normal, it doesnt seem to be doing anything (there are a ton of those errors)
3. Caddy version:
v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=
4. How I installed and ran Caddy:
i use the service to start it
sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
curl -1sLf ‘https://dl.cloudsmith.io/public/caddy/stable/gpg.key’ | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf ‘https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt’ | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy
a. System environment:
Debian Bullseye 11 x64
b. Command:
systemctl start caddy
c. Service/unit/compose file:
Caddyfile
d. My complete Caddy config:
{
on_demand_tls {
ask http://localhost:3000/check/
interval 2m
burst 5
}
}
https://, :80 {
tls {
on_demand
}
reverse_proxy 127.0.0.1:8000
@plausible path /js/script.js /api/event
handle @plausible {
rewrite /js/script.js /js/script.js
reverse_proxy https://analytics.artclass.site {
header_up Host {http.reverse_proxy.upstream.hostport}
}
}
}
# HTTP domains
surfdoge.pro, dogesurf.app, derpman.lol {
reverse_proxy localhost:8000
}
# there are more links but i have too much to put