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.
@kerlosense Your title specifically says “renewing the SSL”. This implies you already issued a certificate previously, which is nearly expired or has expired already and you want to renew this certificate, so it won’t expire (until the next expiry date).
Did you by any chance misunderstood the meaning of “renewing”? And do you want to get a brand new certificate issued for the first time? If yes, please say so, so we can help you with that in stead of renewing.
If you indeed already have a certificate which has expired or is near the expiry date and you’ve previously issued that certificate with certbot, I must refer to my previous post and urge you to read the certbot documentation.
Where in the documentation showed it that command to renew? I don't see it. Please forget your current command and read the documentation above again. It specifically links to the "How to renew" section and the command is even way simpler than the one you're using now.
OK, good, sort of. You’ve issued your certificate previously with the --manual option it seems. Without the proper scripts called with --manual-auth-hook (and --manual-cleanup-hook), it is impossible to automatically renew your certificate like this.
If you cannot automate the adding and removing of the challenge tokens, you cannot automatically renew your certificate. This is not something Let’s Encrypt advices: Let’s Encrypt is all about automation.
Do you remember how you previously managed to do the challenges required for validation of your hostname?