This problem is fixed in the latest version v5.5.7r where the auto function will generate suitable current dates automatically.
A work round for older versions is to specify the generatedcertstart and generatedcertend in unix time in e2guardian.conf.
First find the unix time for your start and end dates with (use todays date for start and add one year to end)
e.g.
[philip@localhost ~]$ date +%s -d "2025-01-31"
1738281600
[philip@localhost ~]$ date +%s -d "2026-01-31"
1769817600
Then add the following to e2guardian.conf:
generatedcertstart = 1738281600
generatedcertend = 1769817600
Then stop e2guardian
Clear out your old generated certs
And start e2guardian.
Regards
Philip
--
E2guardian:
https://groups.google.com/d/forum/e2guardian
Github:
https://github.com/e2guardian/e2guardian
Follow us on twitter:
https://twitter.com/e2guardian
---
You received this message because you are subscribed to the Google Groups "e2guardian" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
e2guardian+...@googlegroups.com.
To view this discussion, visit
https://groups.google.com/d/msgid/e2guardian/c16e0cb1-f278-4a5a-82b2-6b62660eadd9n%40googlegroups.com.