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: www.slcu.nl
I ran this command:
It produced this output: Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: SoHosted
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
With the near-complete lack of information you've provided, I don't think any of us would have any idea what the problem is. What makes you think it has anything to do with certificate renewal? This sounds like a question for your web host.
I received an email few months ago from the community.letsencryt.org with a deadline for renewal of certificate, but was not able to respond on time because of personal problems. Now I try to get access to the website and is not working. So that could be the problem. Thanks
No, you didn't. You may have gotten an email from the community, but it wasn't a renewal notification; that would have been sent by the Let's Encrypt servers, about 20 days before your certificate expired (which was over a month ago).
You don't have a subscription, at least not to Let's Encrypt. Your web host is very badly broken if it's serving that page, but they're the ones who need to renew your cert.
You didn't. You only joined 45 minutes ago, and before that, the community didn't have your email address. You got an email from the Let's Encrypt servers, which are completely different. You apparently ignored it until you realized your site was dead. You now need to go back to your hosting provider and have them fix their mess.