-
certificate is this? certs/192.168.8.32.pem.(tigase auto created )
when visit https://192.168.8.32:18092/index.html, the browser warning me it's a not safe site but can click continue to visit. all https REST interface works ok.
but only the BOSH API can't connect. I'm using strophe.js .
but when using http it works ok. ports as list above. -
certificate is this? certs/192.168.8.32.pem.(tigase auto created )
when visit https://192.168.8.32:18092/index.html, the browser warning me it's a not safe site but can click continue to visit. all https REST interface works ok.
but only the BOSH API can't connect. I'm using strophe.js .
but when using http it works ok. ports as list above. -
when visit https://192.168.8.32:18092/index.html, the browser warning me it's a not safe site but can click continue to visit. all https REST interface works ok.
but only the BOSH API can't connect. I'm using strophe.js .
Quite possibly strophe.js blocks the connection because certificate is self-signed (i.e. those aren't trusted by default).
-
Yesterday, I bought a commercial certificate(based on IP, not domain). and all SSL ports are OK except BOSH。 I confirmed i have a config problem on bosh. But what's a perfect config?
bosh { connections { ports = [ 8090, 18090 ] /** NOT ok */ 18090(){ socket = 'ssl' } /* ok */ 8090(){ } } seeOtherHost {} }
I have a problem with bosh https I cannot open bosh connection: https://192.168.8.32:18090/xmpp-httpbind stroph.js reports: ERR_CONNECTION_CLOSED but when using http (http://192.168.8.32:8090/xmpp-httpbind) it works.
how can i config bosh using https?
Details (please complete the following information):
config.tdsl bosh part: