Application Load balancer SSL error

[pravinvram]

Am trying to create a load balancer with custom domain and currently failing with SSL error. followed the steps in the document, however still no luck. Any help is much appreaciated.

steps followed : https://cloud.google.com/api-gateway/docs/gateway-serverless-neg

error :

Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1028)')

[diannemcm]

Hi @pravinvram,

Welcome to Google Cloud Community!

This error is usually caused by a premature termination of the SSL connection before the handshake is complete or during data transfer.

Go to Load Balancing > Select your load balancer > Frontend Configuration.

• Check the attached SSL certificate. If using a Google-managed certificate, status must be ACTIVE. If it’s FAILED or PROVISIONING, there might be a DNS or domain verification issue.

• Your DNS A record should point to the load balancer’s IP address and has propagated (this can take up to 24-48 hours)

Also indicates a possible mismatch in the SSL/TLS versions supported by your client and server, the load balancer should use a compatible version of TLS (TLS 1.2 or TLS 1.3). You may refer to this conversation.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[pravinvram]

Thanks so much for the reply

• Your DNS A record should point to the load balancer’s IP address and has propagated (this can take up to 24-48 hours)  -  this is done and it's already 48 hours
• It's still in FAILED_NOT_VISIBLE

Any other things I need to check or any known issues would help, currently am stuck.

[diannemcm]

Hi @pravinvram,

Below are other possible reasons as to why you are encountering same issue, which are also stated on this documentation. 

• The domain's DNS record doesn't resolve to the IP address of the Google Cloud load balancer. To resolve this issue, update the DNS records to point to your load balancer's IP address.
• The SSL certificate isn't attached to the load balancer's target proxy. To resolve this issue, update your load balancer configuration.
• The frontend ports for the global forwarding rule do not include port 443 for an SSL proxy load balancer. This can be resolved by adding a new forwarding rule with port 443.

You may also reach out to Google Cloud Support for more detailed insights and assistance. 

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.