Second install of Jitsi meet and still not working well

GentleRV · January 18, 2022, 10:48am

Please guide me how to solve identity problem.
The issue I face is that I can start a room and see myself connected, a new participant start his session with the same room but both can’t see each other and both don’t see the members of the room

This is the content of the jicofo log file in /var/log/jitsi:
Jicofo 2022-01-18 10:34:33.119 INFO: [1] Main.main#49: Starting Jicofo.
Jicofo 2022-01-18 10:34:33.567 INFO: [1] JitsiConfig.#47: Initialized newConfig: merge of /etc/jitsi/jicofo/jicofo.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jicofo/jicofo.jar!/reference.conf: 1
Jicofo 2022-01-18 10:34:33.575 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/jicofo/sip-communicator.properties
Jicofo 2022-01-18 10:34:33.577 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#56: Error loading config file: java.io.FileNotFoundException: /etc/jitsi/jicofo/sip-communicator.properties (No such file or directory)
Jicofo 2022-01-18 10:34:33.579 INFO: [1] JitsiConfig.#68: Initialized legacyConfig: sip communicator props (no description provided)
Jicofo 2022-01-18 10:34:33.579 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
Jicofo 2022-01-18 10:34:34.453 WARNING: [1] FocusManager.start#116: Jicofo ID is not set correctly set (value=0). Configure a valid value [1-65535] by setting org.jitsi.jicofo.SHORT_ID in sip-communicator.properties or jicofo.octo.id in jicofo.conf. Future versions will require this for Octo.
Jicofo 2022-01-18 10:34:34.506 INFO: [1] JicofoServices.createAuthenticationAuthority#178: Starting authentication service with config=AuthConfig[enabled=true, type=XMPP, loginUrl=chat.wetterstof.nl, logoutUrl=null, authenticationLifetime=PT24H, enableAutoLogin=true].
Jicofo 2022-01-18 10:34:34.519 INFO: [1] AbstractAuthAuthority.#112: Authentication lifetime: PT24H
Jicofo 2022-01-18 10:34:35.047 INFO: [1] XmppServices.#48: No dedicated Service XMPP connection configured, re-using the client XMPP connection.
Jicofo 2022-01-18 10:34:35.069 INFO: [1] XmppServices.#63: No Jigasi detector configured.
Jicofo 2022-01-18 10:34:35.114 INFO: [1] BridgeSelector.#88: Using org.jitsi.jicofo.bridge.SingleBridgeSelectionStrategy
Jicofo 2022-01-18 10:34:35.140 INFO: [1] [type=bridge brewery=jvbbrewery] BaseBrewery.#100: Initialized with JID=jvbbrewery@internal.auth.chat.wetterstof.nl
Jicofo 2022-01-18 10:34:35.145 INFO: [1] JicofoServices.#122: No Jibri detector configured.
Jicofo 2022-01-18 10:34:35.146 INFO: [1] JicofoServices.#128: No SIP Jibri detector configured.
Jicofo 2022-01-18 10:34:35.163 INFO: [1] JicofoServices.#143: Starting HTTP server with config: host=null, port=8888, tlsPort=8843, isTls=false, keyStorePath=null, sendServerVersion=true.
Jicofo 2022-01-18 10:34:35.196 SEVERE: [16] [xmpp_connection=client] XmppProviderImpl.doConnect#225: Failed to connect/login: undefined-condition You can read more about the meaning of this stream error at Extensible Messaging and Presence Protocol (XMPP): Core
stream:errorNo stream features to proceed with</stream:error>
org.jivesoftware.smack.XMPPException$StreamErrorException: undefined-condition You can read more about the meaning of this stream error at Extensible Messaging and Presence Protocol (XMPP): Core
stream:errorNo stream features to proceed with</stream:error>

You see here the failed connection from the client, all ports are defined as the handbook indicate.
I searched all documentation about how the internal communication operates but could not find the client credentials.

This is the contents of the jvb.log file located /var/log/
JVB 2022-01-18 10:34:55.323 INFO: [1] JitsiConfig.#47: Initialized newConfig: merge of /etc/jitsi/videobridge/jvb.conf: 1,application.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/application.conf: 1,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-46-g64a7ca8.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-276-gf95fb9d.jar!/reference.conf: 1
JVB 2022-01-18 10:34:55.385 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
JVB 2022-01-18 10:34:55.388 INFO: [1] JitsiConfig.#68: Initialized legacyConfig: sip communicator props (no description provided)
JVB 2022-01-18 10:34:55.392 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
JVB 2022-01-18 10:34:55.421 INFO: [1] MainKt.main#89: Starting jitsi-videobridge version 2.1.607-g153f7e4e
JVB 2022-01-18 10:34:56.081 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Adding a static mapping: StaticMapping(localAddress=91.229.62.14, publicAddress=91.229.62.14, localPort=null, publicPort=null, name=null)
JVB 2022-01-18 10:34:56.169 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.createStunHarvesters: Using 152.67.143.103:443/udp for StunMappingCandidateHarvester (localAddress=91.229.62.14:0/udp).
JVB 2022-01-18 10:34:56.398 INFO: [12] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address 91.229.62.14:35244/udp from STUN server 152.67.143.103:443/udp using local address org.ice4j.socket.IceUdpSocketWrapper@7f2ea66a
JVB 2022-01-18 10:34:56.399 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.maybeAdd: Discarding a mapping harvester: org.ice4j.ice.harvest.StaticMappingCandidateHarvester(face=91.229.62.14:9/udp, mask=91.229.62.14:9/udp)
JVB 2022-01-18 10:34:56.399 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester@26f5850d
JVB 2022-01-18 10:34:56.400 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=955ms). stunDiscoveryFailed=false
JVB 2022-01-18 10:34:56.630 INFO: [18] [hostname=127.0.0.1 id=shard] MucClient.initializeConnectAndJoin#269: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard domain=auth.chat.wetterstof.nl hostname=127.0.0.1 port=null username=jvb mucs=[JvbBrewery@internal.auth.chat.wetterstof.nl] mucNickname=7f6fae1a-5fc6-4c1c-aa58-849250a01044 disableCertificateVerification=false]
JVB 2022-01-18 10:34:56.691 INFO: [1] LastNReducer.#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
JVB 2022-01-18 10:34:56.694 INFO: [1] TaskPools.#81: TaskPools detected 2 processors, creating the CPU pool with that many threads
JVB 2022-01-18 10:34:56.770 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
JVB 2022-01-18 10:34:56.771 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
JVB 2022-01-18 10:34:56.819 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
JVB 2022-01-18 10:34:56.859 INFO: [1] MainKt.main#118: Not starting CallstatsService, disabled in configuration.
JVB 2022-01-18 10:34:56.866 INFO: [1] MainKt.main#127: Starting public http server
JVB 2022-01-18 10:34:56.982 INFO: [1] ColibriWebSocketService.#40: Base URL: wss://chat.wetterstof.nl:443/colibri-ws/default-id
JVB 2022-01-18 10:34:57.027 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @2726ms to org.eclipse.jetty.util.log.JavaUtilLog
JVB 2022-01-18 10:34:57.165 INFO: [18] [hostname=127.0.0.1 id=shard] MucClient.initializeConnectAndJoin#328: Dispatching a thread to connect and login.
JVB 2022-01-18 10:34:57.208 INFO: [1] ColibriWebSocketService.registerServlet#65: Registering servlet at /colibri-ws/*, baseUrl = wss://chat.wetterstof.nl:443/colibri-ws/default-id
JVB 2022-01-18 10:34:57.232 WARNING: [18] [hostname=127.0.0.1 id=shard] MucClient.lambda$getConnectAndLoginCallable$7#618: [MucClient id=shard hostname=127.0.0.1] error connecting
org.jivesoftware.smack.XMPPException$StreamErrorException: undefined-condition You can read more about the meaning of this stream error at Extensible Messaging and Presence Protocol (XMPP): Core
stream:errorNo stream features to proceed with</stream:error>

Please give information how to solve

Freddie · January 18, 2022, 11:38am

What about prosody log?
What distro are you installing on?

GentleRV · January 18, 2022, 11:55am

There is no prosody log file, the /var/log/prosody is empty
The system used is Ubuntu 20.04 and the install is done with the run module from the Jitsi download.

Freddie · January 18, 2022, 12:15pm

What do you mean by this? Did you try to install like an executable?
The fact that you don’t have any prosody log at all is telling. Looks like you’ve been going about the installation wrongly. Use this guide for installing:

GentleRV · January 18, 2022, 12:43pm

yes, and still got it not working, no idea why the client can’t connect.
As told earlier, no idea what the credentials are from this “client” and in which file to find,
With the first install I got no screens to fill-in information like the name of the server, after purging all Jitsi meet installations and start again the install procedure I got the questions to see and could connect by internet (NGINX)., now a second participant in the same room does not become a member, for this I was digging to find out.

emrah · January 18, 2022, 1:10pm

what are the outputs for

systemctl status prosody
systemctl status jicofo
systemctl status jitsi-videobridge2

This installer may be helpful.

GentleRV · January 18, 2022, 4:41pm

:~$ systemctl status prosody
● prosody.service - Prosody XMPP Server
Loaded: loaded (/lib/systemd/system/prosody.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-01-18 10:34:24 UTC; 6h ago
Docs: Documentation – Prosody IM
Main PID: 35270 (lua5.2)
Tasks: 1 (limit: 2177)
Memory: 19.0M
CGroup: /system.slice/prosody.service
└─35270 lua5.2 /usr/bin/prosody

Jan 18 10:34:24 duton-ubuntu prosody[35270]: avmoderation.chat.wetterstof.nl:av_moderation_component info No mu>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: portmanager info Activ>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: conference.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: conference.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: avmoderation.chat.wetterstof.nl:av_moderation_component info Hook >
Jan 18 10:34:24 duton-ubuntu prosody[35270]: breakout.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: breakout.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: breakout.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: conference.chat.wetterstof.nl:muc_domain_mapper info Loadi>
Jan 18 10:34:24 duton-ubuntu prosody[35270]: mod_posix info

systemctl status jicofo
● jicofo.service - LSB: Jitsi conference Focus
Loaded: loaded (/etc/init.d/jicofo; generated)
Active: active (running) since Tue 2022-01-18 10:34:32 UTC; 6h ago
Docs: man:systemd-sysv-generator(8)
Process: 35305 ExecStart=/etc/init.d/jicofo start (code=exited, status=0/SUCCESS)
Tasks: 233 (limit: 2177)
Memory: 239.8M
CGroup: /system.slice/jicofo.service
└─35311 java -Xmx3072m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Djdk.tls.ephemeralDHKeySize=>

Jan 18 10:34:32 duton-ubuntu systemd[1]: jicofo.service: Succeeded.
Jan 18 10:34:32 duton-ubuntu systemd[1]: Stopped LSB: Jitsi conference Focus.
Jan 18 10:34:32 duton-ubuntu systemd[1]: jicofo.service: Found left-over process 13105 (java) in control group while st>
Jan 18 10:34:32 duton-ubuntu systemd[1]: This usually indicates unclean termination of a previous run, or service imple>
Jan 18 10:34:32 duton-ubuntu systemd[1]: Starting LSB: Jitsi conference Focus…
Jan 18 10:34:32 duton-ubuntu jicofo[35305]: Starting jicofo: jicofo started.
Jan 18 10:34:32 duton-ubuntu systemd[1]: Started LSB: Jitsi conference Focus.

systemctl status jitsi-videobridge2
● jitsi-videobridge2.service - Jitsi Videobridge
Loaded: loaded (/lib/systemd/system/jitsi-videobridge2.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-01-18 10:34:54 UTC; 6h ago
Process: 35392 ExecStartPost=/bin/bash -c echo $MAINPID > /var/run/jitsi-videobridge/jitsi-videobridge.pid (code=ex>
Main PID: 35391 (java)
Tasks: 44 (limit: 65000)
Memory: 230.0M
CGroup: /system.slice/jitsi-videobridge2.service
└─35391 java -Xmx3072m -XX:+UseG1GC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Djdk.tls.epheme>

Jan 18 10:34:54 duton-ubuntu systemd[1]: Starting Jitsi Videobridge…
Jan 18 10:34:54 duton-ubuntu systemd[1]: Started Jitsi Videobridge.

will check the installer, thanks

emrah · January 18, 2022, 5:05pm

Is /var/log/prosody writable by prosody?

ls -alh /var/log

GentleRV · January 18, 2022, 5:07pm

yes drwxr-x— 2 prosody adm 4.0K Jan 16 03:01 prosody

GentleRV · January 18, 2022, 5:37pm

I am running the script now.
WHY IS DOES REMOVE NGINX WHO WAS WORKING PEFFECT WITH MY OTHER WEBSITES?

Freddie · January 18, 2022, 5:44pm

Are you hosting this in a cloud solution or on baremetal? Do you have anything else running on the same server?

GentleRV · January 18, 2022, 5:46pm

My own server and yes more then one website already running.
Ubuntu was up to date.

Freddie · January 18, 2022, 5:50pm

Well, that’s almost certainly where the issue lies. Most likely culprits are Nginx misconfiguration and occupied ports. If you’re already running a webserver on the same machine, the default configurations won’t work for you. You have to go through Nginx and make sure everything is proxied correctly. Then make sure required ports are not already being used by other services. Your use case is an outlier, so you’ll need to do a lot of digging on your own. Most people just host Jitsi by itself on a server and much of the support you’ll get will be based on that assumption.

GentleRV · January 18, 2022, 5:52pm

It would be nice to know that on fore hand.
Beside this, now I have to review the good running websites and change nginx to meet the install as before.
All my good working websites are gone, thank you so much
Nothing to see in sites-available.
You make this guy crazy, so much work only for this jitsi stuff todo extra…
My joomla and wordexpress …all gone
This you call support?

Freddie · January 18, 2022, 6:00pm

Huh? You’re blaming me for your Nginx misconfiguration?

shawn · January 18, 2022, 6:02pm

If you are referring to emrah’s installer, you did read the README before running it right?

It does say:

Don’t use this script on a working production server.

I feel for you that you now have to reconfigure nginx, but please don’t take your frustration out on people how are volunteering their free time to help the community.

GentleRV · January 18, 2022, 6:07pm

My NGINX was working fine including with jitsi. I could see the page and adjust settings
It was not NGINX who was the problem, but in the install or package itself.
And yes it is working now as expected.
So somethings else was the problems as I showed with not able to connect a internal client.
Please make the script that only jitsi part is involved and not destroy a production environment which will costs me days to recover

Freddie · January 18, 2022, 6:11pm

eye-roll

{praying}

Oh Lord, please grant me patience… pleaaaaseeee. It’s 2022, I’m trying to do better. Thank You. Amen!

GentleRV · January 18, 2022, 6:37pm

Yes, I feel bad. But now Jitsi work. The script could make copies from the sites-available and other configuration from NGINX before deleting all,
I know you all try to help and appreciate that.
Thanks anyway and hope this script get modified for not to harm others.

emrah · January 18, 2022, 6:56pm

Sorry @GentleRV , I couldn’t guess you are using this server for other work as well but the installer prints a warning before starting and it only runs if it’s allowed.