That boils down to just two certs:
/etc/letsencrypt/live/agshardscapes.com/privkey.pem
/etc/letsencrypt/live/becssafe.jnjinnm.com/privkey.pem
That boils down to just two certs:
/etc/letsencrypt/live/agshardscapes.com/privkey.pem
/etc/letsencrypt/live/becssafe.jnjinnm.com/privkey.pem
I'm seeing correct content here:
I'm seeing "mixed content" that needs fixed, but that's another matter.
That shouldn't exist...
But there is only one listed !
So you interactively created the combined cert then?
If that is ALL the domains, then they ALL need to use the new cert.
And perhaps the certname should have been "ALL".
@griffin I typed certbot and when it displayed all the names of sites available I hit enter without selecting one
@rg305 It is all the domains and subdomains that I know of
Take a minute (or seven) and update all these files:
/etc/apache2/sites-available/emby.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/webmin.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/torrent.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/ourfamily.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/becssafe.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/teatroburlesco.com-le-ssl.conf
/etc/apache2/sites-available/kristol.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/squire.jnjinnm.com-le-ssl.conf
/etc/apache2/sites-available/agshardscapes.com-le-ssl.conf
ensure they use the new cert 
then restart Apache
This was a good idea.
I'm out of likes for now... 
I had deleted all these files and let my latest certbot recreate them.
Also only 1 service is kicking back to the main site as far as I know.
I think your guys' job is done TY SO MUCH for the quick replies
I need to run in a moment, but I feel like things are well underway. Just be sure to fix that mixed content too. No point in getting a cert working and having no padlock to prove it.
Down with "out of likes" 
We need MORE likes! 
Amen, brother. Where did I put that Zelda fairy? 
Glad we of the two-headed-giant-on-speed-persuasion were able to help. 
I know it's not your thing but any idea why this would be kicking back to the root domain?
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName emby.jnjinnm.com
RewriteEngine on
<proxy *>
AddDefaultCharset off
Order Allow,Deny
Allow from all
</proxy>
ProxyRequests Off
ProxyPreserveHost On
ProxyPass "/embywebsocket" "ws://127.0.0.1:8096/embywebsocket"
ProxyPassReverse "/embywebsocket" "ws://127.0.0.1:8096/embywebsocket"
ProxyPass "/" "http://127.0.0.1:8096/"
ProxyPassReverse "/" "http://127.0.0.1:8096/"
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/becssafe.jnjinnm.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/becssafe.jnjinnm.com/privkey.pem
</VirtualHost>
</IfModule>
Still using the wrong cert!
aaahhhhh!!!!!
How does the configuration file for emby.jnjinnm.com differ from the one for kristol.jnjinnm.com?
If you add three backticks before and after the post, maybe I could read it correctly (the curse of discourse!)
```
post
post
post
```
I see it with the backticks, @rg305. You don't?
That starts but never ends...