I have tried to put jitsi meet 7439 version into my server deployment and am facing the issue of showing connection error every new version I’m trying to deploy
I checked the jvb logs and found the error
“A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.”
I think that is safe to ignore. What else do you see in the log?
> VB 2023-03-14 06:12:54.394 INFO: [1] JitsiConfig.#47: Initialized newConfig: merge of /config/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/jitsi-media-transform-2.2-9-g8cded16e.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-58-gf41542d.jar!/reference.conf: 1
> JVB 2023-03-14 06:12:54.431 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /config/sip-communicator.properties
> JVB 2023-03-14 06:12:54.433 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#56: Error loading config file: java.io.FileNotFoundException: /config/sip-communicator.properties (No such file or directory)
> JVB 2023-03-14 06:12:54.438 INFO: [1] JitsiConfig.#68: Initialized legacyConfig: sip communicator props (no description provided)
> JVB 2023-03-14 06:12:54.453 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
> JVB 2023-03-14 06:12:54.499 INFO: [1] MainKt.main#90: Starting jitsi-videobridge version 2.2.9-g8cded16e
> JVB 2023-03-14 06:12:55.391 INFO: [13] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using AwsCandidateHarvester.
> JVB 2023-03-14 06:12:55.509 INFO: [13] org.ice4j.ice.harvest.MappingCandidateHarvesters.createStunHarvesters: Using ip/udp for StunMappingCandidateHarvester (localAddress=172.26.0.6:0/udp).
> JVB 2023-03-14 06:12:55.890 INFO: [14] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address myip:35044/udp from STUN server ip:443/udp using local address org.ice4j.socket.IceUdpSocketWrapper@6c8086ca
> JVB 2023-03-14 06:12:56.045 INFO: [13] org.ice4j.ice.harvest.AwsCandidateHarvester.obtainEC2Addresses: We failed to obtain EC2 instance addresses for the following reason:
> java.lang.IllegalArgumentException: hostname can’t be null
> at java.base/java.net.InetSocketAddress.checkHost(InetSocketAddress.java:149)
> at java.base/java.net.InetSocketAddress.(InetSocketAddress.java:216)
> at org.ice4j.TransportAddress.(TransportAddress.java:61)
> at org.ice4j.ice.harvest.AwsCandidateHarvester.obtainEC2Addresses(AwsCandidateHarvester.java:111)
> at org.ice4j.ice.harvest.AwsCandidateHarvester.getFace(AwsCandidateHarvester.java:153)
> at org.ice4j.ice.harvest.MappingCandidateHarvesters.maybeAdd(MappingCandidateHarvesters.java:189)
> at org.ice4j.ice.harvest.MappingCandidateHarvesters.prune(MappingCandidateHarvesters.java:173)
> at org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize(MappingCandidateHarvesters.java:149)
> at org.jitsi.videobridge.MainKt$startIce4j$1.invoke(Main.kt:239)
> at org.jitsi.videobridge.MainKt$startIce4j$1.invoke(Main.kt:238)
> at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
> JVB 2023-03-14 06:12:56.048 INFO: [13] org.ice4j.ice.harvest.AwsCandidateHarvester.obtainEC2Addresses: String for local IP: null
> JVB 2023-03-14 06:12:56.048 INFO: [13] org.ice4j.ice.harvest.AwsCandidateHarvester.obtainEC2Addresses: String for public IP: myip
> JVB 2023-03-14 06:12:56.049 INFO: [13] org.ice4j.ice.harvest.MappingCandidateHarvesters.maybeAdd: Discarding a mapping harvester: org.ice4j.ice.harvest.AwsCandidateHarvester@3ba17cc8
> JVB 2023-03-14 06:12:56.050 INFO: [13] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester@6c10463c
> JVB 2023-03-14 06:12:56.051 INFO: [13] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=1498ms). stunDiscoveryFailed=false
> JVB 2023-03-14 06:12:56.581 INFO: [1] LastNReducer.#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
> JVB 2023-03-14 06:12:56.604 INFO: [1] TaskPools.#87: TaskPools detected 8 processors, creating the CPU pool with that many threads
> JVB 2023-03-14 06:12:56.606 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient.initializeConnectAndJoin#279: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=shard0 domain=auth.meet.jitsi hostname=xmpp.meet.jitsi port=5222 username=jvb mucs=[jvbbrewery@internal-muc.meet.jitsi] mucNickname=8a4d02627ddf disableCertificateVerification=true]
> JVB 2023-03-14 06:12:56.711 INFO: [1] HealthChecker.start#117: Started with interval=60000, timeout=PT1M30S, maxDuration=PT3S, stickyFai3ba17cc8lures=false.
> JVB 2023-03-14 06:12:56.795 WARNING: [21] MucClient.createXMPPTCPConnectionConfiguration#115: Disabling certificate verification!
> JVB 2023-03-14 06:12:56.830 WARNING: [1] UlimitCheck.printUlimits#111: Running with open files limit 1048576 (hard 1048576), thread limit null (hard null). These values are too low and they will limit the number of participants that the bridge can serve simultaneously.
> JVB 2023-03-14 06:12:56.840 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
> JVB 2023-03-14 06:12:57.141 INFO: [1] MainKt.main#120: Not starting CallstatsService, disabled in configuration.
> JVB 2023-03-14 06:12:57.174 INFO: [1] MainKt.main#129: Starting public http server
> JVB 2023-03-14 06:12:57.408 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient.initializeConnectAndJoin#341: Dispatching a thread to connect and login.
> JVB 2023-03-14 06:12:57.871 INFO: [1] ColibriWebSocketService.#46: Base URL: wss://dev.meet.revidd.space/colibri-ws/172.26.0.6 Relay URL: null
> SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> JVB 2023-03-14 06:12:58.454 INFO: [1] ColibriWebSocketService.registerServlet#85: Registering servlet with baseUrl = wss://dev.meet.revidd.space/colibri-ws/172.26.0.6, relayUrl = null
> JVB 2023-03-14 06:12:58.517 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient$2.connected#312: Connected.
> JVB 2023-03-14 06:12:58.517 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient.lambda$getConnectAndLoginCallable$9#637: Logging in.
> JVB 2023-03-14 06:12:59.323 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient$2.authenticated#318: Authenticated, b=false
> JVB 2023-03-14 06:12:59.448 INFO: [1] MainKt.main#147: Starting private http server
> JVB 2023-03-14 06:12:59.675 INFO: [21] [hostname=xmpp.meet.jitsi id=shard0] MucClient$MucWrapper.join#761: Joined MUC: jvbbrewery@internal-muc.meet.jitsi
> JVB 2023-03-14 06:13:00.922 WARNING: [1] org.glassfish.jersey.server.wadl.WadlFeature.configure: JAXBContext implementation could not be found. WADL feature is disabled.
> JVB 2023-03-14 06:13:01.105 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored.
> JVB 2023-03-14 06:13:01.106 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
> JVB 2023-03-14 06:13:56.849 INFO: [26] VideobridgeExpireThread.expire#140: Running expire()
> JVB 2023-03-14 06:14:56.848 INFO: [26] VideobridgeExpireThread.expire#140: Running expire()
These are the jvb logs I see
What version are you deploying now? How does the generated jvb.conf file look like in the container?
I am deploying docker jitsi meet 7648-3 version
I’d suggest you deploy the latest. We don’t support old releases, sorry.
But the jitsi meet 7287 version which we have been using until past month has been working fine in our servers.
docker jitsi meet repository itself states in the readme file that it supports versions greater than 7439