<p>I have a AWS <strong>LoadBalancer</strong> which created using <code>Kube</code>, <code>Kops</code> and <code>AWS</code>.
protocl type for the <strong>ELB</strong> is <strong>tcp</strong>. this work fine for <code>http</code> requests, means I can access my site with <strong><a href="http://testing.example.com" rel="nofollow noreferrer">http://testing.example.com</a></strong>. Now I tried to add <strong>SSL</strong> for this <strong>ELB</strong> using <strong>ACM</strong> <code>(Certificate manager)</code>. I added my Domain details <code>example.com</code> and <code>*.example.com</code> by requesting a <strong>public Certificate</strong>. it created successfully and domain validation is also success.</p>

<blockquote>
  <p>Then I tried to add this ssl to my ELB like below.</p>
</blockquote>

<ul>
<li>went to my ELB and selected the ELB.</li>
<li>Then went to Listeners tab and Added SSL to it like below.</li>
</ul>

<p><a href="https://i.stack.imgur.com/Za3k7.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Za3k7.png" alt="enter image description here"></a></p>

<p>and <strong>ELB</strong> description is like below.</p>

<p><a href="https://i.stack.imgur.com/XUzVT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XUzVT.png" alt="enter image description here"></a></p>

<p>I cannot access the <a href="https://testing.example.com" rel="nofollow noreferrer">https://testing.example.com</a>, it hangs for few minutes and nothing happens. what is going on here. hope your help with this.</p>

<p>In the Listener configuration, you are forwarding the default HTTP port <code>80</code> to port <code>30987</code> on the back-end server. So this tells me that the back-end server is listening for HTTP requests on port <code>30987</code>.</p>

<p>You then added an SSL listener on the default port <code>443</code> but you are forwarding that to port <code>443</code> on the back-end server. Do you have something on your back-end listening on port <code>443</code> in addition to <code>30987</code>?</p>

<p>The most likely fix for this is to change the SSL listener on the load balancer to forward to port <code>30987</code> on the back-end by setting that as the "Instance Port" setting.</p>
