You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[mcu]
# The type of the MCU to use. Currently only "janus" and "proxy" are supported.
# Leave empty to disable MCU functionality.
#type =
type = janus
url = wss://127.0.0.1:8189
skipverify = true
log Could not initialize janus MCU (x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs) will retry in 16s
It's possible to disable cert verification ?
The text was updated successfully, but these errors were encountered:
This is not possible right now, pull requests welcome :-)
Besides, if both are running on the same host (which is the usual deployment), there is no need to have a secure connection between the signaling server / -proxy and the Janus server.
@fancycode thx for your fast reply.
The goal is to do TLS end to end but ofc this is obviously secure on same host :)
But Pull request is welcome ofc :)
Janus ws config
`#
general :
{
json = "indented";
ws = "yes";
ws_port = "8188";
ws_ip = "127.0.0.1";
wss = "yes";
wss_ip = "127.0.0.1"
wss_port = "8189"
};
admin :
{
admin_ws = "no";
admin_ws_port = "7188";
admin_wss = "no";
};
certificates :
{
cert_pem = "/etc/ssl/certs/ssl-cert-snakeoil.pem";
cert_key = "/etc/ssl/private/ssl-cert-snakeoil.key";
};
`
log
Could not initialize janus MCU (x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs) will retry in 16s
It's possible to disable cert verification ?
The text was updated successfully, but these errors were encountered: