Let's encrypt cert not renewed.

[shortthefomo]

I setup my hosts with the let's encrypt certificate....

but digging into the logs now I see the cert was not auto renewed according to https://docs.evernode.org/en/latest/platform/sashimono/ssl.html

I find these errors in my evernode log log file.

Dec 11 19:06:09 zaouli node[1360171]: 20241211 18:06:09 [err] -------------------------------------------------------
Dec 11 19:06:09 zaouli node[1360171]: 20241211 18:06:09 [err] --  Your SSL certificate has expired, Please renew!  --
Dec 11 19:06:09 zaouli node[1360171]: 20241211 18:06:09 [err] -------------------------------------------------------
Dec 11 19:06:09 zaouli node[1360171]: 20241211 18:06:09 [dbg] Skipping reputation sender due to ineligibility for reputation.
Dec 11 19:19:40 zaouli node[1360171]: 20241211 18:19:40 [dbg] Skipping reputation contract preparation since there's no universe info for the moment 8725.
Dec 11 20:06:09 zaouli node[1360171]: 20241211 19:06:09 [dbg] Checking IPV4 support...
Dec 11 20:06:09 zaouli node[1360171]: 20241211 19:06:09 [dbg] Checking version compatibility...
Dec 11 20:06:09 zaouli node[1360171]: 20241211 19:06:09 [dbg] Checking SSL certificate validity...

• how do I get let's encrypt to reissue a certificate now? I don't find anything in the documentation on what todo in the case were lets encrypt was used but has failed to renew the certificate?

[shortthefomo]

Right I think I got to the bottom of this, no where in the docs does it say port 80 hast to be left open (I run a web server on 80) so I shut that down for the install and put it back after.

My thesis is that port 80 need to remain open when let's encrypt tries to renew the SSL.

I managed to transfer and then reinstall disabling port 80 temporarily to complete install.. and got it issued again.

[shortthefomo]

managed to fix this issue was I run caddyv2 on the box to reverse proxy other ports and caddy automagically "grabs" port 80 so creating a reverse proxy for the Evernode instance and then bundling and manually using evernode applyssl fixes this issue.