Ok I made the changes this is my setup I hope it works
UPDATE
When I made the CNAME change it took off the SLS
UPDATE
When I made the CNAME change it took off the SLS
2 Likes
and the Loadbalancing is default https setup to the bucket on google storage
UPDATE
The CNAME to c.storage.googleapis.com gave it the same SLS error. So I switched it back.
regardless if you type
www.akiraleoshoots.com
or akiraleoshoots.com
it will still direct it to akiraleoshoots.com with https://
so I dont think you can goto www.akiraleoshoots.com because it will automatically direct it to akiraleoshoots.com without the www
please correct me if I'm wrong.
2 Likes
Having a CNAME from www.akiraleoshoots.com (left side) to akiraleoshoots.com (right side) will not affect your SSL functionality at all compared with having an A record for www.akiraleoshoots.com that points to the same IP address as the A record for akiraleoshoots.com.
The problem you might be facing with the 301 redirect is that your host is redirecting without serving the correct SSL certificate for www.akiraleoshoots.com. Hard to say without the functionality currently in place to test.
2 Likes
Everytime I put the cname to Google storage apis. It gives an invalid cert. The redirect on the www always goes to the naked domain. You can't actually goto the www . But balancer sees the cert active when when I direct the www to the balancer. Removing the cname entirely has helped I think because it's already using c.storage.googleapis.com because that's the front end config to the bucket for the https. It's all way over my head at this point. I got my end result. It's 301 redirecting any http to https. And any www. Or root domains are going to a valid cert. I think if I hosted my website through firebase or another hosting provider this would be alot more simple.
Update: I changed the prefix to full redirect seems to work. Let me try to change the cname again.
Update 2:
Nope puts my whole website down plus no sls
2 Likes
While I'm happy that you got the result you wanted, I'm very confused as to why making a simple change to your DNS settings to add a CNAME record for www pointing to your naked domain name (not c.storage.googleapis.com) would have any impact on the functionality of your SSL. All of this happens in your DNS and has nothing to do with your hosting, load balancer, or application.
The whole purpose of a CNAME (canonical name) record is to treat what's on the left (www.akiraleoshoots.com) as an alias for the true (canonical) name that's on the right (akiraleoshoots.com). When anything requests the A record for www.akiraleoshoots.com, the CNAME will cause a DNS lookup for the A record of akiraleoshoots.com. Thus, the exact same result will be returned as if you only had the same A record for www.akiraleoshoots.com. Make sense? Your load balancer will be completely unaware that any of this is happening.
The 301 redirect, which is a completely different thing from the CNAME, should be happening inside the load balancer causing any request for http://akiraleoshoots.com to be redirected to http://www.akiraleoshoots.com and any request for https://akiraleoshoots.com to be redirected to https://www.akiraleoshoots.com. Note that this 301 redirect is not a "full domain name redirect" as some hosters will call it. This is a configured redirect inside the load balancer.
2 Likes
Wow thanks I was confused about the cname. So I used the cname for the naked domain. Seems like it came with the right result.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.