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.
Could you please copy/paste the full output? This is a little bit too little to work with to be honest.
Also, if we look at the certificates for your domain, it seems previously you actually did have the www subdomain included. However, in your most recent certificate, it has vanished? How did that happen?
Usually, one just runs certbot renew and nothing would change.. But for some reason, your certificate did change, which most likely would have been a manual step.
Now reload or restart Apache and use certbot to expand your current certificate (if certbot asks, say it to not redirect http to https because you are already doing it).
First step is to actually have a www subdomain configured in your Apache. Please run apachectl -S, notice that there is no www subdomain mentioned, add the appropriate amount of correct ServerAlias directives to your Apache, run apachectl -S again to check if the www subdomain is present now and try certbot again.
I'm afraid you did it wrong, you didn't expand your current certificate, you created a new one only valid for www.ragnarok-rp.com but not for raganarok-rp.com so now you will have problems to access your site using only the apex domain ragnarok-rp.com
If I attempt to use www.ragnarok-rp.com and ragnarok-rp.com when it asks me which I want to activate HTTPs for, it says in the command line it is "invalid".
The www subdomain is missing from your port 80 virtualhost. Although it seems the certbot apache plugin now actually does recognise a www subdomain nonetheless.