LetsEncrypt node certificate renews, but type is "Requested"

Support
, , ,
21

Saved to a file:

Hope this works! :wink:

1 Like
22

Latest core release 3.12.2 has a bug. I think you should have it. In this case you can downgrade to 3.12.1 with a command like:

api-cli run update-core --data '{"core_url":"ghcr.io/nethserver/core:3.12.1", "nodes":[1],"force":true}'

Replace the node Id with your value(s).

Then restart Mail as explained before.

Bug reference: Requested/Renewed TLS certificate not applied · Issue #7679 · NethServer/dev · GitHub

Released Release 3.12.3 · NethServer/ns8-core · GitHub
:warning: After Core Update, if the application still presents the old certificate, restart it from Software Center.

1 Like
23

That has fixed it. I knew the errors started after I updated, just Mail or Core I didn’t know. I won’t update core for the next couple weeks.

Thanks David!

1 Like
24

It’s a core 3.12.2 bug. I added a get_certificate function to the Python agent library, but that name was already used. My mistake /cc @stephdl

A fix for this will be released as core 3.12.3.

Edit: Released Release 3.12.3 · NethServer/ns8-core · GitHub
After Core Update, if the application still presents the old certificate, restart it from Software Center.

2 Likes
25

true
..one task, one fully qualified domain name

1 Like
26

We’re only human — we make mistakes. But what truly matters is how we handle them.
In the middle of the big Nethesis event, @davidep and @mrmarkuz stepped up and fixed the bug.

20251010_084739
20251010_0847391920×2560 258 KB

5 Likes
27

no wonder i was facing issues. THanks for the fix

1 Like