The certificates mounted in app container in /certs are getting dumped by traefik-certs-dumperproperly but mailu doesn't scan for them changing.
behavior:
If we have a container running for a really long time (2 months+ uptime because that's how long the letsencrypt certs are valid), the smtp/imap servers will serve the certificate that was loaded 2 months ago which will have expired by this time. Even though the file has been rotated by traefik-certs-dumper.
workaround:
restart the app container every 2 months to load the new certificates lol
The certificates mounted in `app` container in `/certs` are getting dumped by `traefik-certs-dumper`properly but mailu doesn't scan for them changing.
behavior:
If we have a container running for a really long time (2 months+ uptime because that's how long the letsencrypt certs are valid), the smtp/imap servers will serve the certificate that was loaded 2 months ago which will have expired by this time. Even though the file has been rotated by `traefik-certs-dumper`.
workaround:
restart the `app` container every 2 months to load the new certificates lol
Mailu docs recommend running this after certs are regenerated: docker exec mailu_front_1 nginx -s reload
Is it possible that's enough, if the front container is indeed terminating TLS even for IMAP/SMTP connections? Maybe it's something we can add to the traefik-certdumper config? Or a separate service using inotifywatch to detect changes in certs and reload when there are new ones?
Amazing troubleshooting @knoflook, nice one!
[Mailu docs recommend](https://mailu.io/master/maintain.html#external-certs) running this after certs are regenerated: `docker exec mailu_front_1 nginx -s reload`
Is it possible that's enough, if the `front` container is indeed terminating TLS even for IMAP/SMTP connections? Maybe it's something we can add to the `traefik-certdumper` config? Or a separate service using `inotifywatch` to detect changes in certs and reload when there are new ones?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The certificates mounted in
appcontainer in/certsare getting dumped bytraefik-certs-dumperproperly but mailu doesn't scan for them changing.behavior:
If we have a container running for a really long time (2 months+ uptime because that's how long the letsencrypt certs are valid), the smtp/imap servers will serve the certificate that was loaded 2 months ago which will have expired by this time. Even though the file has been rotated by
traefik-certs-dumper.workaround:
restart the
appcontainer every 2 months to load the new certificates lolAmazing troubleshooting @knoflook, nice one!
Mailu docs recommend running this after certs are regenerated:
docker exec mailu_front_1 nginx -s reloadIs it possible that's enough, if the
frontcontainer is indeed terminating TLS even for IMAP/SMTP connections? Maybe it's something we can add to thetraefik-certdumperconfig? Or a separate service usinginotifywatchto detect changes in certs and reload when there are new ones?