I can try to give that a go. But this isn't an Apache forum, so most of us aren't experts! What I put below works, though it might not be the only way to do things.
As others have said, your certificate doesn't cover "www.lab.addmoreroutes.com", just "lab.addmoreroutes.com". That's fine, I only cover "darksteve.tk" and not"www.darksteve.tk" with my certificate. Just be aware that adding "www" will throw an error if you use it.
Your Apache vhosts should contain something like the following:
<VirtualHost *:80>
ServerName lab.addmoreroutes.com
Redirect permanent / https://lab.addmoreroutes.com/
</VirtualHost>
<VirtualHost *:443>
DocumentRoot /path/to/your/website
ServerName lab.addmoreroutes.com
SSLEngine on
SSLCertificateFile "/etc/letsencrypt/live/lab.addmoreroutes.com/fullchain.pem"
SSLCertificateKeyFile "/etc/letsencrypt/live/lab.addmoreroutes.com/privkey.pem"
</VirtualHost>
The first section will redirect all http traffic (unencrypted port 80) to your https site (encrypted port 443). You posted the location of your certificates so I added the correct path for those, but only you know where your website is located, so you need to fill out the path for that yourself.
I hope that helps, and gives you a starting point. Good luck!
EDIT: Certbot needs access to port 80 in order to renew. The above works for me and also allows renewing without any issues. I've been renewing since 2016!
Also, you can renew by using "certbot renew". If you add that to a weekly cron job, it will be visually obvious what the command does and it will renew your certificate once the certificate has only 30 days left. You can run "certbot renew" as often as you like, it won't hassle the Let's Encrypt servers until your certificate is close to expiry. (That is, provided you don't "--force" a renewal, which you shouldn't need to do under most circumstances.)
EDIT2: I almost forgot! Always do a backup of the files you edit! This is especially important when you're still learning. You might break an functioning site while fixing your non-functioning site. Just a simple "cp vhosts.conf vhosts.conf.bak" or something will do. I'm on FreeBSD, not linux, so I can't say for sure what your files are called!