My problem is, i can't renew the certificates with certbot. I have an error "Instruction non permise (core dumped)" something like "illegal instruction (core dumped)".
I use a NGINX server on a Rocky linux 9.
I have 2 or 3 subdomains and authelia, but one is not protected by it and the problem is similar.
I move all files in /etc/letsencrypt/renewal/ until test only the one that have a bypass with authelia and problem still the same.
It's something new, everything worked by the past.
You'll probably need to supply a bit more information. Logs, certbot and nginx version numbers, command you used etc. There's a useful questionnaire when you start a new topic
[Edit: illegal instruction sounds a bit architecture related, E.g. cpu type but it may not be]
Certbot is a Python application. If such an error occurs when running Python, to me this means something is seriously wrong. And probably not Certbot itself, but something bigger.
If you can explain more, please. I followed a tutorial from digital ocean, because i didn't find my distribution on certbot website. I fear to ignore to much things and i'm ok to learn more.
I think i resolved my problem by reinstalling packets and nginx plugin. All websites are up now.
I don't know at all what happened, i installed it there is few months, i let notes but i forget a lot of what i did.
The following screenshot, which you deleted from the post above my last one, indicates that you were attempting to run certbot without an authenticator (for acquiring a certificate) or an installer (for installing a certificate):
I don't remember a specific issue that has caused this error recently.
In general, this kind of problem can occur when a Linux distribution is somehow inappropriate for the hardware environment that it's running on (like a 64-bit Linux distribution installed on a 32-bit server, or a Linux distribution for one kind of ARM CPU installed on a server that has a different kind of ARM CPU).
It can also occur when there is some kind of hardware failure (like defective RAM chips or an overheating CPU), or, less likely, if there's an undetected disk error that corrupts files on disk somehow.
I'm sure there are other possible causes that I'm not thinking of, but those feel like the likeliest ones offhand. Can you check what kind of CPU and hardware you have on your server and see if there are any indications that your Linux distribution is somehow mismatched to the hardware environment or that the hardware itself is having reliability problems? Can you run a RAM test or some kind of CPU stress test on the same hardware?