0

I set up SSL encryption for my Elastic Beanstalk environment's load balancer. When I visit the base url it works. So

https://example.com

Works. But when I visit:

https://www.example.com

the connection is not secure. I can't find the reason for this. I did get the certificate both for example.com and *.example.com.

I configured both addresses record sets over ip4 in the Route 53 hosted zones.

halfer
  • 19,824
  • 17
  • 99
  • 186
J. Hesters
  • 13,117
  • 31
  • 133
  • 249
  • 1
    The exact information about why the connection is not believed to be secure would be helpful. – Michael - sqlbot May 27 '18 at 16:35
  • Thanks for your help. I can't reproduce the issue anymore, since I resolved the issue by adding explicitly adding `www.example.com` to my certificate. – J. Hesters May 27 '18 at 16:38

2 Answers2

0

I resolved the issue by adding explicitly adding www.example.com to my certificate.

I don't like this workaround, but it does the trick I guess...

J. Hesters
  • 13,117
  • 31
  • 133
  • 249
0

Wildcard record should work all case. You should check your Route53. Also, make sure don't use the Uppercase character in load balancer naming.

Aman Juman
  • 404
  • 5
  • 12