dingsenyou

I have same problem, and found that issus only occur when the https certificate were self-signed or issues from private CA. The https site using public certificate issued from public CA will work without problem.

I believe the situation were stuck because firefox ask for user interaction when it receive a non-public CA issues SSL certificate. Since RDM call it from API, there is no way to pass the user interaction to FF.

I have try to browser the self-signed site within standalone firefox and force FF to trust this site first, but still no help to embedded inside RDM.

Chrome has no problem to view the same self-signed SSL site. It looks like capable to bypass the user interaction step.

Is there any solution to this problem?