diff --git a/404.html b/404.html index cd5c4be9..df680def 100644 --- a/404.html +++ b/404.html @@ -5,7 +5,7 @@
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/rpc.sentinel.yournodename.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for rpc.sentinel.yournodename.com and api.sentinel.yournodename.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Congratulations, all renewals succeeded:
/etc/letsencrypt/live/rpc.sentinel.yournodename.com/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This indicates that your certificate has been successfully renewed.
Finally, restart the NGINX service to apply the renewed certificates:
-sudo systemctl stop nginx.service
sudo systemctl start nginx.service
Your remote procedure call (RPC) and API should now be accessible again via HTTPS.