For the life of me, I can't figure out what I am doing wrong. I followed the AWS documents to add SSL on a classic ELB (I tried the NLB which still failed for us).
Basically, we have a webserver which listens on port 80. I want to have SSL termination happen at the ELB.
I added the ELB correctly, added a security group for it's network interfaces (even tried a dangerous allow all inbound outbound). I also tried this for the instance's security group.
When I would navigate to https://mytestserver.com/resource it would default to http - but for the login page, would show https. Once logged in, it would use http after.
I read mixed things in the docs/online, that said for the SSL termination, you need to have a 443 elb listener port --> instance port 80 AND also, another rule with 80 ELB listener port ---> instance port 80.
If I try to remove the rule for the 80 elb listener port --> instance port 80, I can login -- but the page hangs.
It is loading some flash components, so I did make sure to enable the ports for that. I even tried a temporary 'allow' all, as previously mentioned for the security group for the LB and the instance.
It's making me think that the instance's web server (this is an external customer webserver which is running an application on of our team uses, which is using jetty) does not like some sort of header injection that is happening.
When I removed the listener for port 80 on the elb, I wiresharked my computer, and it showed that it kept trying to reach on port 80 to the elb....any ideas!?
P.S. I should mention, without the SSL stuff in place, the http version of the site works fine.