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 https://www.wowza.com/docs/how-to-request-an-ssl-certificate-from-a-certificate-authority 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.
[HTML]
cupertinoEncryptionBaseURL
[/HTML]
Adding or removing this value makes little difference.
[HTML]netstat -tulp | grep https
tcp 0 0 *:https : LISTEN 6186/java [/HTML]
likewise
[HTML]netstat -tulpn | grep 443
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 6186/java [/HTML]
and
[HTML]netstat -tulpn | grep 1935
tcp 0 0 0.0.0.0:1935 0.0.0.0:* LISTEN 6186/java [/HTML]
and
[HTML]netstat -tulp | grep http
tcp 0 0 ds6880.dreamservers:www : LISTEN 5836/httpd-argon-ht
tcp 0 0 *:https : LISTEN 6186/java[/HTML]
Also when I point to this domain reefs.reefcam.tv https://www.geocerts.com/ssl_checker and I type in reefs.reefcam.tv and use 443 certificate appears valid. Like I am returning in Firefox and Chrome. This test works on Chrome.
When I do this test http://www.sslshopper.com/ssl-checker.html#hostname=reefs.reefcam.tv it is failing with about the same problem I am describing.
Anyone have any ideas why the SSL is not working? Your help would save me a lot of time and money.
Thank You, John Anderson http://www.vermontinternetdesign.com