SSL connection can't be established

I have the following situation with my website https://www.domain.com works fine but https://domain.com can't establish a secure connection. 

I have a google managed certificate whit the following hostnames domain.com and *.domain.com.

In the Domain Provider I have A records for @ to point to  <IP Load Balancer> and * to point to  <IP Load Balancer>.  

In the Load Balancer a default 301 redirect rule to www.domain.com is set.

I am not sure what am I missing here in order for the http://domain.com and https://domain.com to work as well.

Thank you.

Solved Solved
6 2 159
1 ACCEPTED SOLUTION

Hi @razvan_todea ,

This is challenging to troubleshoot without more visibility of what you're trying to achieve but here are some steps you can check to troubleshoot the issue.

  1. Make sure that the certificate status and the domain status are in ACTIVE status.
    You can check the status of your certificate by running the following command:
    gcloud compute ssl-certificates describe CERTIFICATE_NAME \
        --global \
        --format="get(managed.domainStatus)"
  2. Update your load balancer as the Google-managed SSL certificate must be associated with the load balancer.
  3. Verify the the target proxy association between the SSL certificate and the target proxy.
  4. Make sure you update the DNS A and AAA records to your load balancer's IP address.

You can check this documentation for your reference.

I hope you find this information useful.

View solution in original post

2 REPLIES 2

Hi @razvan_todea ,

This is challenging to troubleshoot without more visibility of what you're trying to achieve but here are some steps you can check to troubleshoot the issue.

  1. Make sure that the certificate status and the domain status are in ACTIVE status.
    You can check the status of your certificate by running the following command:
    gcloud compute ssl-certificates describe CERTIFICATE_NAME \
        --global \
        --format="get(managed.domainStatus)"
  2. Update your load balancer as the Google-managed SSL certificate must be associated with the load balancer.
  3. Verify the the target proxy association between the SSL certificate and the target proxy.
  4. Make sure you update the DNS A and AAA records to your load balancer's IP address.

You can check this documentation for your reference.

I hope you find this information useful.

After 2-3 days it started to work for some users without changing anything, so I believe it might be a propagation issue since the redirect is performed now in most of the cases.