Skip to main content
Participant
May 11, 2010
Question

is my SSL Cert Exception something i've done wrong?

  • May 11, 2010
  • 1 reply
  • 920 views

Hi,

I'm hoping someone here can shed some light on a problem I've had for a number of days now.

We have a flash based video player that uses flv's provided by FMS3.5 on the same web box (IIS) with a number of websites hosted on the same box.

I'm getting a browser based SSL certificate exception on our production server, but only when the website/video player is viewed from outside the corporate firewall. (Usually it's the other way around)

"A secure connection with this site cannot be verified..." and it gives the url of another site that's hosted on the same IIS box.

If I view the swf in the flash player or from behind the corp firewall I get no error, however if I view it from outside I get the error. If I accept the SSL cert I still get a connectionError.

I've tried adding a crossdomain policy file and even adding the path to that file to the server.xml config for FMS but still get the error/issue.

I'm stumped - hoping someone here can shed some light on the problem.

Regards

RR

    This topic has been closed for replies.

    1 reply

    May 11, 2010

    NAT issue perhaps? From outside the firewall, is port 443 NAT'd to the IIS IP?

    redrazorsAuthor
    Participant
    May 11, 2010

    thanks for the response!

    443 is bound to another domain in IIS (which is the cert it's trying to use)

    secure.com:443

    unsecure.com:80 ...  which uses FMS and is now trying to use the cert from secure.com

    Should I be binding a secure port to the domain I want to use FMS on and then declaring that in the FMS config files?

    This is all like another language to me

    Another question which springs to mind is will this problem always have existed or is it something that could have changed?

    Also is there anyway to dissable the server using ssl?

    May 12, 2010

    Thanks Jay,

    I'm looking into getting the suggested changes implimented.

    Still can't figure out why it would work from inside the firewall but not from the web?

    Cheers

    RR


    I'd need to know all of your configurations to be sure, but I suspect that  port 1935 (the default port the flashplayer tries first to connect to FMS) is open for requests from inside the firewall, but blocked to the internet. If the port 1935 connection fails, the flashplayer will then try port 80.

    If my suspicions are correct, that's why it works from within the firewall. Since neither apache nor IIS bind to port 1935, FMS is able to bind to 1935, and therefore requests on 1935 go to FMS as expected.