janus-gateway and ipv6 issues

319 views
Skip to first unread message

Hector Colina

unread,
Jul 16, 2019, 11:27:31 AM7/16/19
to meetecho-janus
Using Debian/Ubuntu on vultr VPS provider, I get:

[FATAL] [transports/janus_http.c:janus_http_init:784] Couldn't start webserver on port 8088

I've disabled ipv6 from grub (GRUB_CMDLINE_LINUX="XXXX ipv6.disable=1") but janus webserver service can't start

[WARN] libwebsockets has been built without IPv6 support, will bind to IPv4 only WebSockets thread started [FATAL] [transports/janus_http.c:janus_http_init:784] Couldn't start webserver on port 8088...

Enabling ipv6 allow start the service

[WARN] libwebsockets has been built without IPv6 support, will bind to IPv4 only libwebsockets logging: 0
WebSockets server started (port 8188)...
[WARN] Secure WebSockets server disabled
[WARN] Admin WebSockets server disabled
[WARN] Secure Admin WebSockets server disabled
JANUS WebSockets transport plugin initialized!
Loading transport plugin 'libjanus_http.so'...
HTTP webserver started (port 8088, /janus path listener)...

but port 8088 is using ipv6 protocol:

tcp6 0 0 :::8088 :::* LISTEN 0 20312 1077/janus

ipv6 is disable on janus.jcfg configuration file.

Using ipv6 we get next issue on sip gateway:

WebRTC error... "getUserMedia not available"

So, does we have and configuration issue or it is a bug?

Thank you.

Lorenzo Miniero

unread,
Jul 17, 2019, 4:28:10 AM7/17/19
to meetecho-janus
You're mixing different things in the same post that have little to do with each other, actually. 8088 is the port used by libmicrohttpd for HTTP/REST, not libwebsockets. Not sure why you mention getUserMedia here, as that's a completely different thing: I guess you mean the demos tell you there's no getUserMedia, which 99% means you've opened a page via HTTP and not HTTPS.

Lorenzo 
Reply all
Reply to author
Forward
0 new messages