Hi I have a bit of a problem here. I went ahead and installed our SSL certificate onto our server.
https://reefs.reefcam.tv/Cayman by clicking on that link. It should produce the wowza default page on the https:// connection. In fact if I put this into internet explorer or into firefox, I appear to make a successful connection on port 443 by using
https://reefs.reefcam.tv if I load a playlist in ie or ff, they are downloaded, I can see they are accessing
http://reefs.reefcam.tv:443 which appears to be the port that SSL has binded too.
However, when I try to open the https:// url inside of chrome or any type of video player embeded into the page, I cannot connect to the SSL socket at all. There is no errors in the logs. according to firefox and internet explorer the certificate that is set up on the domain is correct. I used these instructions here
http://www.wowza.com/forums/content.php?128 and go the certificate installed on the server. I've already been through the keytool a million times and their does not appear to be any problem with the certificate. I did however, find a thread that says to add something like this into Application.xml for one of the apps.
Hi, I solved my own problem. It appears that there was a problem with the SSL handshake. Proved to not be a problem on some systems. However, changing the iptables on my server worked wonders. This is one of those servers where some people have access to it through a control panel, some people have access to it through the bash shell. I use the server from the Bash Shell and people with access to the server through the default control panel can over ride each others settings. There was a hidden set of iptables rules that was causing the server to reject certain requests to it.
So simply flushing the[HTML] iptables -F[/HTML] then [HTML]iptables-restore /root/rules.bak[/HTML] worked wonders from this job. So I will just leave this posted for the next guy, with a similar problem.