If the certificate was created with “
certbot --apache” or just “
certbot”, Certbot would continue to use the apache plugin when renewing the certificate, yes.
What web server is listening on port 80 now? Port 443?
Are you still using Apache at all?
Is there a port forwarding or reverse proxy configuration involved?
What does “
sudo certbot certificates” show?
What are the contents of the files in
Depending on the situation, you might want to validate using something like Certbot’s webroot plugin, or you might want to continue using the apache plugin for validation. (For example, you might have an Apache virtual host that otherwise just redirects to HTTPS, or reverse proxies to Node.js.)
You’ll probably also want to set up a Certbot deploy hook to reload or restart the Node.js server so that it uses the new certificate.
Can you also answer most of the questions below?
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. https://crt.sh/?q=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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
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):