Closed andrewmarkforbes closed 1 month ago
Does anyone have any ideas on this? It seemed to start with the latest mailcow update (version 2024-07ish to 2024-08a, and it's still happening. It seems to cycle through archiving ALL the additional SAN SSL certs on the server, a couple at a time, and once all the SSL certs have been archived and re-implemented, acme will run once or twice and report that "Certificates were successfully validated, no changes or renewals required, sleeping for another day." Then on the next run through, it'll start them all over again
After restarting the acme container a BUNCH more times, this issue seems to have resolved itself. The last 10 restarts have all resulted in "Certificates were successfully validated, no changes or renewals required, sleeping for another day."
Fingers crossed it stays that way.
I also noticed my server had IPv6 connectivity problems, which I just fixed, and acme is still now fine. Maybe that connectivity problem at the time of the last update triggered this whole thing. anyway, I guess this issue should be closed now.
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian Bookworm
Server/VM specifications:
11GB RAM, 4 CPU cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
KVM
Docker version:
27.1.1
docker-compose version or docker compose version:
v2.29.1
mailcow version:
2024-08a
Reverse proxy:
N/A
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check: