Attempting to connect to my Jetty server to debug a new RTC Extension I was working on in RTC 4.0.1, failed with an SSL error with all my current Browsers, Chrome and Firefox without being able to find a workaround in the browsers. How to work around that issue?
This problem only occurs when using the RTC SDK for RTC versions prior to RTC 6.x. It will affect all of these versions. It does not prevents performing the RTC Extensions Workshop since most of the tasks there can be done using the Eclipse UI. However, it impacts developing RTC Server extensions and test them properly, if it is necessary to use the Web UI because it is impossible to go into the web UI to test.
The problem I ran into is basically related to Chrome Does Not Work With RTC Debug Server on Jetty. However, it turns out that the work around described there does no longer work. Neither Tomcat nor Chrome allow to enable SSL V3 anymore showing errors like this in FireFox.
The messages contain text like
Unable to Connect Securely Firefox cannot guarantee the safety of your data on localhost:7443 because it uses SSLv3, a broken security protocol. Advanced info: ssl_error_unsupported_version
This webpage is not available ERR_SSL_VERSION_OR_CIPHER_MISMATCH Hide details A secure connection cannot be established because this site uses an unsupported protocol.
The only ways around I found so far are:
- Use the internal browser of the RTC Eclipse client of the version of RTC you are trying to extend
- Use a browser that does not block SSL such as Chromium in a version that allows the work around described in Chrome Does Not Work With RTC Debug Server on Jetty
You can download Chromium of various versions here. Version 44.0.2385.0 does still work for me and it does not update automatically.
The development team tracks the issue in Defect 354890. As long as there is no other solution, use the workarounds provided above. As soon as there are new news, I will try to provide the details.