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.
Hi @bsoranno and Welcome to the community!
Do you have a vhost configured for http://fvtt.computerserviceswinona.com/ or is the subdomain possibly configured as an alias in your running config??
Please share the output of:
apache2ctl -t -D DUMP_VHOSTS
also I notice you should upgrade your version of certbot
Thanks
Normally, I'd say: Just do what you did before to get the previous cert (again - one more time).
But seeing:
It's difficult to be sure about what you did previously and thus impossible to know for sure if that will work again going forward.
As there is no HTTP vhost config that covers any of the three FQDNs mentioned, I can only assume you may have used --webroot authentication OR you have since manually modified/deleted some of the vhost config file(s).
So...
If FVTT is NOT going to serve the exact same content as the other two, then you must make a separate HTTP vhost config to handle it.
Once you have that config in place, you can then use certbot to obtain a cert for it and have it make the HTTPS vhost config for you (if you don't want to do it yourself).