Today instantly SSL certificate problems

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: amiga-dresden.de

I ran this command: ---

It produced this output: ---

I'm using nginx proxy manager for managing certificates, so can't say much at time.
Only, since today is an old certificate shown if I try to load the site.
The Browswer output:
|Ausgestellt am|Sonntag, 20. Juli 2025 um 13:57:06|
|Gültig bis|Samstag, 18. Oktober 2025 um 13:57:05|

But up to yesterday all was ok and nobody has done anything on certificates here.
The nginx proxy manager has the followin information: Expieres: 15th July 2026, 4:03 pm
what should the correct data.
If I try to generate the certificate new, there is no error coming up, but also don't see any change in browser and also no change in proxy manager. :frowning:

Is there a problem in the let's Encrypt database since today on this entry?
All other domains are running without problems here, all with let's Encrypt certificates on the same server and reverse proxy.

Has anyone an idea?

Greetings :slight_smile:

2

Oh, now all my sites have old certificates.
Up to now was all ok there ...!? ;(

3

There is no such thing. Certificates are signed and issued. They are not kept in some sort of database at Let's Encrypt to which browsers can connect, the server which was issued the certificate sends it to the browser in the connection handshake.

And your server somehow is sending an ancient certificate. Which is weird indeed. But well, that's NPM for you I guess (nobody around here likes that piece of software..)

Maybe an old backup was put back? :person_shrugging:

4

Yes, after the first fail I restart the VM and wasn't coming up so right so I have reinstall a backup.
But the data of the backup should had the correct certificates on board and all outdated in the future. So I wondering, why are upcoming nearly one year outdated certificates from anywhere?

Oh, is this software so bad?
Is there anything new what I could using for that and what can I do for renew my certificates?

Thank you for clearing anything in understanding the technique! :slight_smile:

5

It's very difficult to debug for us volunteers, as it has not really implemented the whole ACME part properly.

I don't know, I'm not really into webservers or reverse proxies any more.

6

Oh, yes, that's a good point if it is difficult to debug! :frowning:
A reverse proxy here is the only method what makes sense for any servers at home. But I try to fix it or set it up for new. Hoping I'll find a way ...

Thank you!
With luck has anyone else an idea?

7

It was running many years now in this configuration, thats, why I'm wondering about this instantly upcoming chaos from nowhere ...

8

That might be a very good question for the NPM community.

9

Oh, ok, I will ask there ... was thinking, it's more a problem of let's Encrypt.

10

Oh, have seen now, all my certificates are correct now again! ... wtf!?
I've done nothing since yesterday. All certificates are new now.
Ok, hopefully it works well in the future! :smiley:

11

NPM works in mysterious ways :man_shrugging: Quite literally..