Firefox can't establish connection to wss://localhost:7443/websocket

[byrim...@gmail.com]

Hi Norman and all,

      In a secure environment, we are not able to open websocket connection from fire-fox browser. Our domain has self signed cert and the same cert is used for secure web sockets. 

      The combination is https+ wss. From a client, the call to secure web sockets is wss://localhost:7443/websocket. We have found a log in firefox saying "Firefox can't establish a connection to the server at wss://172.20.36.97:7443/websocket. ". 

      In order to make it work in Firefox, the client  has to do an extra step i.e., opening https://localhost:7443/ in the browser. With this extra step,the cert is accepted. Then he can go back and open the application and application can establish a connection to wss in Firefox. But this solution doesn't seem to be fruitful. 

       Without doing any changes it works in Chrome, Opera, IE10.

      

      Is this browser problem ? Or Implementation problem ?

Regards,

Monika.

[Norman Maurer]

As far as I can tell it's a "firefox problem":

https://bugzilla.mozilla.org/show_bug.cgi?id=594502

---

Norman Maurer

nma...@redhat.com

JBoss, by Red Hat

--
 
---
You received this message because you are subscribed to the Google Groups "Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netty+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[byrim...@gmail.com]

Hi Norman,

       Thanks for the quick reply. I have seen the link. How can we avoid this issue ? If we can go with a trusted certificate instead of self signed certificate, can we overcome this problem ? (I just want to confirm before buying a trusted certificate, otherwise purchasing certificate from CA will be in vain.)

Regards,

Monika.

[Norman Maurer]

I did not check it here but yeah I think trusted certificate should be the way to go..

---

Norman Maurer

nma...@redhat.com

JBoss, by Red Hat

[byrim...@gmail.com]

 

Thanks Norman,

       I will test this issue with a trusted certificate and 'll let you know the progress. Please keep giving your valuable suggestions till this issue closed.

Regards,

Monika.

[a.shas...@gmail.com]

Hi Norman,

I'm facing similar issue which is described in above thread chain. I have a signed certificated from trusted CA. When we try to create socket connection using WSS protocol, connection gets opened and closed with a IOException immediately. 

Exception that was raised here is,  "IOExceptions has been raised  Received fatal alert: bad_certificate". Could you please tell me what is causing the socket connection to be closed immediately.

Chrome and IE browser's are not having any issues while creating socket connection using WSS protocol with the same signed certificate.

Thanks in advance

A Shashank

[john mayer]

please try trusted certificate. with trusted certificate, netty websocket working fine for all browser.