My domain is: www.akiraleoshoots.com
I ran this command:
Load balancer generated cert
It produced this output:
Ssl invalid.
My web server is (include version):
Idk
The operating system my web server runs on is (include version):idk
My hosting provider, if applicable, is:
Google domains
I can login to a root shell on my machine (yes or no, or I don't know):
Idk
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Google cloud console
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Another note my https ip goes to a 404.page for Google.
You seem to have generated seven certificates. The problem is that the one you have installed only covers akiraleoshoots.com and thus does not cover www.akiraleoshoots.com.
How can I get one . Because my www is directed to my cname www.akiraleoshoots.com. to my c.storage.googleapis.com. I generated one through my load balancer but it can't get directed to the www because of the cname
Why do akiraleoshoots.com (35.190.117.101) and www.akiraleoshoots.com (108.177.122.128) point to two different webservers? Aren't they supposed to both point to the same website?
This whole question is entirely unrelated to Let's Encrypt. That said, I think you need to specify multiple domains when configuring your Frontend Configuration https settings (Google Managed Certificate) e.g. www.akiraleoshoots.com akiraleoshoots.com. For the purposes of a certificate, www.domain.com and domain.com are very different things, so you have to specify them both.
Yeah I understand. The thing is that the load balancer cant see the new cert I created for www.akiraleoshoots.com therefore it says FAILED_NOT_VISIBLE. I know its not related but thats the reason why if you type www.akiraleoshoots.com youre not getting a HTTPS or a redirect to HTTPS because the CNAME is www is being used by c.storage.googleapis.com. Also I'm using those settings I know that this question is now not viable to what my original question was.
UPDATE:
I don't know what I did. But I deleted the CNAME, directed it to the same A ip address as the load balancer and used www as the prefix. And then made another load balancer to redirect it to HTTPS with prefix redirect. Now the website is working. I assume the load balancer had the as the front end c.storage.googleapis.com so it didn't need to use it. But the website seems to have all the certs even typing www or naked domain.
I'm still very confused as to why you would want the apex (naked) domain name and the www subdomain name to point to two different websites (like they do now). Is this desired?
Normally, www.akiraleoshoots.com should just be a CNAME to akiraleoshoots.com. Since they're both pointing to the same IP address now, I'm wondering if there are different Virtual Hosts on the back end serving different content.
I just checked a few different ways. I'm rather baffled by why it's different in my Samsung Internet browser. Seems to be the same in other browsers. Possibly my cache didn't fully clear. Not sure.
Weird. I removed the original cname. And it fixed it self. Have you tried a different internet provider? This problem is probably beyond certs now xD. The naked or root domain both point to the sls website
I wouldn't worry too much here. Probably just me. I would, however, change the A record for www.akiraleoshoots.com to a CNAME record pointing to akiraleoshoots.com. This just ensures that the address for www.akiraleoshoots.com stays in lockstep with any address changes for akiraleoshoots.com. Also, you want to 301 redirect akiraleoshoots.com to www.akiraleoshoots.com (or vice versa) for SEO purposes (canonical URL). Otherwise, search engines will split your traffic between the "two" websites.
Seems to be the same in other browsers. Possibly my cache didn't fully clear. Not sure. 
