![]() * NOTE: If you add a new option please remember to document it here: * eslint-disable comma-dangle, no-unused-vars, no-var, prefer-template, vars-on-top */ They too, though, ignore tons of details that would most definitely be worth at least mentioning. Not that this would be a problem with the two "Jitsi Meet for FreeBSD" guides I found they are of course specifically for FreeBSD. Still, it just hurts the brain to see "guides" that assume only one possible approach to the process - which now days often means not just the LAMP stack, but even worse: Docker. Not to mention keeping the instructions up to date. I understand it's painful to write instructions about how to (exactly) install and configure anything that's even a bit more complicated than a basic daemon. Many times, it has something to do with documentation - or, not exactly the lack of it, but the lack of descriptions that would allow admins new to that particular system to quickly grasp precise enough understanding of how (exactly) the different components "talk" with each other, what is their exact role in the big picture, etc. Still, there are some of these products that really make me pull my hair off. I've been in hosting for two decades and consider myself very good at figuring stuff out. Yes, the guides being outdated is certainly at least part of the problem.Īlso, Jitsi Meet is one of those otherwise wonderful open source products out there, that are a pain in the * to actually fully understand. I'm working on those now and if/when I find a setup that works, I'll try to remember to post it here. Trying to sort that out next.ĮDIT: The cipher suite related log entries apparently are normal and do not signal a problem. To find out what's going on, I added this to the jicofo_start() function in /usr/local/etc/rc.d/jicofo:Īpparently, that results in all (actually) available cipher suites being rejected. The trust store file, by the way, should be /usr/local/etc/jitsi/jicofo/truststore.jks - not /usr/local/etc/ssl/java.pem (as claimed by the Honeyguide instructions). In my case, the above "fix", however, resulted in a new problem:Īccording to file is readable by the Jicofo process though, so something else must be wrong. While many would (for a good reason) say that this is not a real solution, you can disable SSL/TLS certificate checks for Jitsi video bridge to Prosody by adding the below line (in bold) to the section apis => xmpp-client => configs => xmpp-server-1 in nf: Prosody only shows this when I try to connect to the jitsi-server: $SmackWrappedException: : PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested targetįollowed by a loooong list of java exceptions. Jicofo 19:17:29.004 SEVERE: XmppProvider.doConnect#179: Failed to connect/login: : PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested target Most likely host it will contain only one ingress with content will contain your main cluster domain and array.īase_url - is the domain which will be used in links generation, most of the time is the same as Īfter you are finished with tuning, install the chart on your cluster.Jicofo 19:17:28.889 INFO: JicofoServices.#134: Starting HTTP server with config: host=null, port=8888, tlsPort=8843, isTls=false, keyStorePath=null, sendServerVersion=true, =, tlsCipherSuites=. Main entry here is host (for example, ""), others are optional. Lobby.ingresses: is an array of parameters for Kubernetes Ingress. For more information, refer to JITSI setup. ![]() ![]() _url and _private_key are optional and used to configure on-premise audio/video calls. : use this option to add the content of your relay_auth_private.pem. If you don't know what to put in YOUR_RELAY_DOMAIN and CLUSTER_DOMAIN, look for ingressHostPattern in my_relay_values.yaml.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |