Janus https help

919 views
Skip to first unread message

Jerson Luiz de Paula Junior

unread,
Jun 26, 2017, 10:57:48 AM6/26/17
to meetecho-janus

I'm trying to set up janus days with https but with no success. Any help is welcome, follow below my settings:

https://pastebin.com/W49yKD6d

Mirko Brankovic

unread,
Jun 26, 2017, 3:27:03 PM6/26/17
to meetecho-janus
Insecure response means that janus didn't reply with secure response to proxied browser request.
Make sire you poimt https transport on janus side to self signed certificates from janus repo or the apache ones...

On Jun 26, 2017 16:57, "Jerson Luiz de Paula Junior" <jerson...@gmail.com> wrote:

I'm trying to set up janus days with https but with no success. Any help is welcome, follow below my settings:

https://pastebin.com/W49yKD6d

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

Mirko Brankovic

unread,
Jun 26, 2017, 3:29:35 PM6/26/17
to meetecho-janus
Sorry for typos, hackers android keyboard is really small :)

Lorenzo Miniero

unread,
Jun 26, 2017, 5:01:13 PM6/26/17
to meetecho-janus
You've created a proxy in nginx, but are still connecting to https://server:8089 instead of :443 as it should.

L.

Firas Abd Alrahman

unread,
Jun 26, 2017, 7:24:30 PM6/26/17
to meetecho-janus

LetsEncrypt ssl for ubuntu / apache ( I hope this will help)


it can be like that,
sudo apt-get update
sudo apt-get install python-letsencrypt-apache
sudo letsencrypt --apache -d DOMAIN.COM

Then find the generated ssl 
certificate: /etc/letsencrypt/live/DOMAIN/cert.pem
Private Key : /etc/letsencrypt/live/DOMAIN/privkey.pem

update certificates janus.cfg (for me/opt/janus/etc/janus/janus.cfg)

and for janus.transport.http.cfg (for me /opt/janus/etc/janus/janus.transport.http.cfg)

enable https=yes
and update the certificate sections with new file paths.
this worked for me for secure web socket mode, but it should work with https as well.

remember to restart janus server.

Jerson Luiz de Paula Junior

unread,
Jun 27, 2017, 7:31:35 AM6/27/17
to meetecho-janus
I use certificates cert_pem = /opt/janus/share/janus/certs/mycert.pem and cert_key = /opt/janus/share/janus/certs/mycert.key of janus in apache certificates and works fine now! Is it correcly?

Mirko Brankovic

unread,
Jun 27, 2017, 7:42:09 AM6/27/17
to meetecho-janus
should be ok for development :)
so mostlikely your apache certs weren't there :)

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



--
Regards,
Mirko

Lorenzo Miniero

unread,
Jun 27, 2017, 8:55:16 AM6/27/17
to meetecho-janus
Are you connecting to port 443 from the browser or not? If not, then aligning the certificates is not the solution. You're simply not having the connection to 8089 certificate rejected because it was already accepted when connecting to the web page (see the related discussion on https://janus.conf.meetecho.com/docs/deploy ). Proxying only makes sense if you connect to the proxy to talk to Janus, instead of connecting to Janus itself.

L.

Jerson Luiz de Paula Junior

unread,
Jun 27, 2017, 8:58:49 AM6/27/17
to meetecho-janus
Tanks  for help. Janus, asterisk 13 and IBM voice recognition works fine!


Em segunda-feira, 26 de junho de 2017 11:57:48 UTC-3, Jerson Luiz de Paula Junior escreveu:

Jerson Luiz de Paula Junior

unread,
Jun 27, 2017, 9:04:20 AM6/27/17
to meetecho-janus
I I'm not using port 443 only 8189 and it's running without proxy.
Look my demo: https://volts.eng.br

Jerson Luiz de Paula Junior

unread,
Jun 27, 2017, 9:10:03 AM6/27/17
to meetecho-janus
I'm actually using https 443 in the browser and janus https = yes 8189 without proxy


Em segunda-feira, 26 de junho de 2017 11:57:48 UTC-3, Jerson Luiz de Paula Junior escreveu:
Reply all
Reply to author
Forward
0 new messages