![]() Note: I’m using JWT enabled in docker jitsi meet as well. I tried explicitly logging into the prosody container and adding the jigasi user and password to the auth domain but unfornutely it still does not work.Ĭannot load details for contact : XMPPError: item-not-found - cancelĬan someone help point out potential reasons as to why Jigasi wouldn’t connect to prosody? I noticed that here there is a statement that could mean the jigasi XMPP user wasn’t created or wasn’t properly authenticated but can’t really understand why. Jigasi 10:23:06.862 INFO: .registrationStateChanged().120 REG STATE CHANGE -> RegistrationStateChangeEvent Jigasi 10:23:06.858 SEVERE: ().219 Could not read avatar image from file Insufficient rights to access this file in current user's home directory: .FileAccessServiceImpl.getPrivatePersistentFile(FileAccessServiceImpl.java:171)Īt .(AvatarCacheUtils.java:190)Īt .(AvatarCacheUtils.java:77)Īt .$n(GlobalDisplayDetailsImpl.java:377) The MUC functionality is provided by the XMPP server (prosody). Jitsi Meet conferences are associated with an XMPP Multi-User Chat (MUC) room. Jigasi 10:23:06.763 INFO: .CallControlMucActivator.joinCommonRoom().289 Joining call control room: 10:23:06.852 SEVERE: .retrieveDetails().369 Cannot load details for contact : XMPPError: item-not-found - cancel JItsi COnference FOcus is a signaling server, one of the backend components in the Jitsi Meet stack. Now the actual final error which in my understanding is the one preventing from registering against Prosody: a:377) Author: Yana Stamcheva See Also: Serialized Form Nested. ![]() The main security configuration form panel. I still couldn’t understand quite well what is this jitsi0.pcap file and what it’s meant for, but checking the /config/log/ directory shows that this file really does not exist. Jitsi: the OpenSource Java VoIP and Instant Messaging client. Jigasi 10:23:02.457 SEVERE: .() Failed to register custom Renderer .PulseAudioRenderer with JMF.įurther down in the logs I see this which I now think that can be impactful: : Insufficient rights to access this file in current user's home directory: /config/log/jitsi0.pcap Not sure if this will impact Jigasi registration with prosody Read here in the forum in other threads that this is most likely harmless. As soon as someone catches on that you’re using Jitsi, all the source is open and available and this defeats the purpose of you obsuring your local copy. The full log is at the end of the thread.Ī few outstanding errors that I see in the Jigasi logs are: Jigasi 10:23:00.356 SEVERE: () Error creating c lib instance for fixing file permissions` Personally, I don’t think security via obscurity is going to get you very far. The problem I’m encountering is with running Jigasi in kubernetes / docker-lib-jitsi. I’m following the steps described here: Guide for setting up Jigasi with Voximplant ![]() I have been working on Jitsi for a few months now and we have a deployment of all components in a baremetal Kubernetes cluster (this will also work for any provider as well, the only change would be the load balancer nodes IMO) I will certainly try to contribute as I learn. Kudos to everyone in this brilliant community especially who spends a shit ton of time and effort helping people here. I’ve encountered countless posts here helping troubleshoot a lot of things so far. This is where you need to add proxy_protocol to both of the listen lines.Hi guys, first of all. I figured out how to get nginx to log the clients IP address to access.log (rather than logging 127.0.0.1):Įdit /etc/nginx/modules-enabled/nfĪdd to the server ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |