1. Caddy version
v2.4.1
(upgraded from v2.3.0 in attempt to fix)
a. System environment:
Ubuntu 18 server
b. Command:
caddy reload
d. My complete Caddyfile or JSON config:
3speak.co {
redir https://3speak.tv{uri}
}
3speak.tv {
reverse_proxy http://127.0.0.1:9400
}
3speak.online {
redir https://3speak.tv{uri}
}
studio.3speak.co {
redir https://3speak.tv{uri}
}
studio.3speak.tv {
reverse_proxy http://127.0.0.1:3005
}
live.3speak.co {
reverse_proxy http://127.0.0.1:3000
}
live.3speak.tv {
reverse_proxy http://127.0.0.1:3000
}
standupx.3speak.co {
reverse_proxy http://127.0.0.1:8080
}
standupx.3speak.tv {
reverse_proxy http://127.0.0.1:8080
}
wsb.3speak.co {
reverse_proxy http://[::1]:5000
}
wsb.3speak.tv {
reverse_proxy http://[::1]:5000
}
img-standupx.3speak.co {
reverse_proxy http://[::1]:3030
}
img-standupx.3speak.tv {
reverse_proxy http://[::1]:3030
}
spk.network {
root * /var/www
encode gzip
file_server
}
3. The problem I’m having:
Firefox is showing the error SEC_ERROR_REVOKED_CERTIFICATE. I’m assuming the OSCP has invalidated the certificate and I’m wondering what the best way to force caddy to regenerate them is? I have considered deleting ~/.local/share/caddy/certificates but don’t want to risk it.
5. What I already tried:
I updated caddy to the latest version and restarted the service reloaded the Caddyfile. I tried to work out how to enforce letsencrypt encryption as the current certificate is ZeroSSL. I think some people have mentioned rate limits and I know there’s a lot of domains here so that could be it.