# HTTPS + SSL works on all browsers EXCEPT Google Chrome (both desktop/mobile) (ERR\_TIMED\_OUT) **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [March 2, 2018, 10:26pm UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852 "2018-03-02T22:26:43Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Rogier\_Tuinte1](https://avatars.discourse-cdn.com/v4/letter/r/a88e4f/32.png) [@Rogier\_Tuinte1](https://community.wowza.com/u/Rogier_Tuinte1)\ **Post date:** [March 2, 2018, 10:26pm UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852/1 "2018-03-02T22:26:43Z")
The title is pretty self-explanatory - I’m able to view the stream using the Wowza player on an HTTPS page with Safari and IE. Chrome refuses to work using HTTPS. It happens both using the embedded Wowza player as well as using a Chrome plugin to load the HLS stream directly from the URL. HTTP works fine. The error it prints is just an ERR\_TIMED\_OUT error. Certificates are working properly, I’m sure of that. Any suggestions? ---
**Author:** ![Jermaine\_Hemby](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@Jermaine\_Hemby](https://community.wowza.com/u/Jermaine_Hemby)\ **Post date:** [March 3, 2018, 4:10pm UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852/2 "2018-03-03T16:10:26Z")
Hello, Thanks for contacting the Wowza Community. The error looks to be the cert does not meet the browser security standards. Can you try the Wowza provided [Streamlock Service](https://www.wowza.com/docs/how-to-get-ssl-certificates-from-the-streamlock-service) as a test? If this works, you will need to improve the security of your current cert. regards, Jermaine ---
**Author:** ![Rogier\_Tuinte1](https://avatars.discourse-cdn.com/v4/letter/r/a88e4f/32.png) [@Rogier\_Tuinte1](https://community.wowza.com/u/Rogier_Tuinte1)\ **Post date:** [March 3, 2018, 10:24pm UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852/3 "2018-03-03T22:24:19Z")
Hi Jermaine, thanks for the reply. My SSL certificate is provided by Streamlock. ---
**Author:** ![Jermaine\_Hemby](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@Jermaine\_Hemby](https://community.wowza.com/u/Jermaine_Hemby)\ **Post date:** [March 4, 2018, 6:41pm UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852/4 "2018-03-04T18:41:17Z")
Hello, Thanks for the update and info. can you confirm the Chrome version you are testing with? thanks, Jermaine ---
**Author:** ![Pavel\_Frkal](https://avatars.discourse-cdn.com/v4/letter/p/cc9497/32.png) [@Pavel\_Frkal](https://community.wowza.com/u/Pavel_Frkal)\ **Post date:** [December 8, 2020, 7:04am UTC](https://community.wowza.com/t/https-ssl-works-on-all-browsers-except-google-chrome-both-desktop-mobile-err-timed-out/50852/5 "2020-12-08T07:04:17Z")
Hello, if anyone comes to this thread via google or otherwise, be warned that even with OpenJDK 11 (tested with 8 as well) TLS 1.3 is not fully functional even with Wowza version 4.8. It works in most browsers just fine but with few Chrome versions (namely under W10) it simply keeps timing out from the browser perspective. We were able to capture the SSL handshake - Chrome asks for 1.3 handshake, then downgrades to 1.2 and finally sends TCP FIN regardless (all doe within milliseconds however the browser times out after 10+s). We’ve ended up disabling TLS 1.3 in the java.security to resolve this. Just to mention older versions of WMS do need this corrections as well if you update your Java as TLS 1.3 gets automatically enabled by the java update however Wowza doesn’t respond about one third of all TLS 1.3 handshakes for any clients we’ve tested.