Videobridge does nothing, no port listening, i dont know why

Hello, I hope someone can help me. I’ve been trying to set up a Jitsi-meet server for days now and it just won’t work.

Whats works:

  • Jitsi Web Interface
  • Join to Room
  • Chat

What works not

  • Autio/Video

I used netstat, and there is no port tcp:4443 and no port udp:10000 open.

netstat -tulpe
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
tcp        0      0 0.0.0.0:xmpp-server     0.0.0.0:*               LISTEN      prosody    143929     97/lua5.2           
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      root       139954     34/sshd: /usr/bin/s 
tcp        0      0 0.0.0.0:xmpp-bosh       0.0.0.0:*               LISTEN      prosody    141952     97/lua5.2           
tcp        0      0 localhost:5347          0.0.0.0:*               LISTEN      prosody    141949     97/lua5.2           
tcp        0      0 0.0.0.0:xmpp-client     0.0.0.0:*               LISTEN      prosody    143933     97/lua5.2           
tcp6       0      0 [::]:www-http           [::]:*                  LISTEN      root       150058     304/httpd           
tcp6       0      0 localhost:http-alt      [::]:*                  LISTEN      jvb        149939     206/java            
tcp6       0      0 [::]:xmpp-server        [::]:*                  LISTEN      prosody    143928     97/lua5.2           
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      root       139963     34/sshd: /usr/bin/s 
tcp6       0      0 [::]:ddi-tcp-1          [::]:*                  LISTEN      jicofo     151755     261/java            
tcp6       0      0 [::]:https              [::]:*                  LISTEN      root       150070     304/httpd           
tcp6       0      0 [::]:xmpp-bosh          [::]:*                  LISTEN      prosody    141951     97/lua5.2           
tcp6       0      0 localhost:5347          [::]:*                  LISTEN      prosody    141950     97/lua5.2           
tcp6       0      0 [::]:xmpp-client        [::]:*                  LISTEN      prosody    143932     97/lua5.2           
udp6       0      0 [::]:44339              [::]:*                              jicofo     148192     261/java 

I use ArchLinux with the AUR git Build of the packages “jitsi-meet-git”, “jitsi-videobridge-git”, “jicofo-git”.

/etc/jitsi/videobridge/jitsi-videobridge.conf

JVB_HOSTNAME=meet.mydomain.de
JVB_HOST=localhost
JVB_PORT=5347
JVB_SECRET=12345
JVB_OPTS="--apis=xmpp,"
JAVA_SYS_PROPS="-Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi\
 -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=videobridge\
 -Dnet.java.sip.communicator.SC_LOG_DIR_LOCATION=/var/log/jitsi-videobridge\
 -Djava.util.logging.config.file=/etc/jitsi/videobridge/logging.properties"
VIDEOBRIDGE_DEBUG_OPTIONS="-Djava.util.logging.config.file=/etc/jitsi/videobridge/logging.properties -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=jitsi-videobridge -Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc"

/etc/jitsi/videobridge/sip-communicator.properties

org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.meet.mydomain.de/.*
org.jitsi.impl.neomedia.transform.srtp.SRTPCryptoContext.checkReplay=false
org.jitsi.videobridge.TCP_HARVESTER_PORT=4443

journalctl -u jitsi-videobridge

Jan 20 22:07:12 meet.mydomain.de systemd[1]: Started Jitsi Videobridge.
Jan 20 22:07:12 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:12.828 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of application.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/application.conf: 1,
Jan 20 22:07:12 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:12.833 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#51: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
Jan 20 22:07:12 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:12.835 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
Jan 20 22:07:12 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:12.837 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.122 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=265ms).  stunDiscoveryFailed=false
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.171 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 0 maxEnforcedLastN: 40
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.174 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.194 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 524288 (hard 524288), thread limit 63934 (hard 63934).
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.195 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.299 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.302 WARNING: [1] MainKt.main#91: Statistics are not enabled, publishing updated presence will not work.
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.304 INFO: [1] MainKt.main#110: Not starting CallstatsService, disabled in configuration.
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.307 INFO: [1] MainKt.main#128: Not starting public http server
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.308 INFO: [1] MainKt.main#137: Starting private http server
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.362 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @910ms to org.eclipse.jetty.util.log.JavaUtilLog
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.431 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_27
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.939 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any 
Jan 20 22:07:13 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:13.939 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any
Jan 20 22:07:14 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:14.327 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@2c779e5{/,null,AVAILABLE}
Jan 20 22:07:14 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:14.340 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@1be2019a{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
Jan 20 22:07:14 meet.mydomain.de jvb.sh[817]: 2021-01-20 22:07:14.341 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @1889ms

i would be very grateful if anyone has any ideas. I really don’t know where the fault could be.

post your jvb.log file. Note that jvb not listening on port 10000 does NOT necessarily mean that it’s not operational
Verify also that your connection is properly secured (the green lock on the browser). Jitsi is a webrtc system, if connection is not secure, media access is not granted by the browser.
For the record, I don’t think that your org.jitsi.videobridge.TCP_HARVESTER_PORT=4443 parameter is doing anything, TCP is disabled by default for the bridge (and it’s a feature, it’s intentional as it’s not optimal and not used widely)

Thanks for your answer.

  1. SSL is Working. I use a wildcard cert for meet.domain.de and auth.meet.domain.de in in Apache and Prosody.
  2. There is no jvb.log. There are only 2 empty folders “jicofo” and “jitsi-videobridge” but no log files. My only log is in systemd.

SSL working: I take it that your browser is asking your for media authorization then ?

no log files: with Debian packaging, logs are going to /var/log/jitsi -> jicofo.log and jvb.log. I wonder why it would be made different on another distro. Anyway, what’s the log for systemd ? and do you see indeed at least 2 running Java processes, one for jicofo and one for videobridge ? if you see videobridge, what are the content of:
config, jvb.conf, sip-communicator.properties
in the videobridge home directory ?
if you don’t see the videobridge, can you try to start it with jvb.sh script ?

  1. SSL: Yes, i can even see myself. Everyone can see itself.

  2. I have no file named “config” or “jvb.conf”. My Files are:

  • jitsi-videobridge.conf
  • sip-communicator.properties
  • logging.properties

The content of the jitsi-videobridge.conf and sip-communicator.properties are in my first post.

  1. start with:
    [jvb@meet user]$ /usr/share/jitsi-videobridge/jvb.sh --host=localhost --domain=meet.domain.de --port=5347 --secret=12345 --apis=xpmm,

Output:

2021-01-21 18:44:01.379 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of 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-1.0-214-gfc6cda2.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-22-g67ffceb.jar!/reference.conf: 1
2021-01-21 18:44:01.383 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#40: net.java.sip.communicator.SC_HOME_DIR_LOCATION not set
2021-01-21 18:44:01.384 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
2021-01-21 18:44:01.385 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
2021-01-21 18:44:01.633 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using AwsCandidateHarvester.
2021-01-21 18:44:01.695 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 0 maxEnforcedLastN: 40
2021-01-21 18:44:01.698 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
2021-01-21 18:44:01.714 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 524288 (hard 524288), thread limit 63934 (hard 63934).
2021-01-21 18:44:01.716 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
2021-01-21 18:44:01.815 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
2021-01-21 18:44:01.818 WARNING: [1] MainKt.main#91: Statistics are not enabled, publishing updated presence will not work.
2021-01-21 18:44:01.820 INFO: [1] MainKt.main#110: Not starting CallstatsService, disabled in configuration.
2021-01-21 18:44:01.823 INFO: [1] MainKt.main#128: Not starting public http server
2021-01-21 18:44:01.823 INFO: [1] MainKt.main#137: Starting private http server
2021-01-21 18:44:01.878 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @894ms to org.eclipse.jetty.util.log.JavaUtilLog
2021-01-21 18:44:01.950 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_275-b01
2021-01-21 18:44:02.155 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.maybeAdd: Discarding a mapping harvester: org.ice4j.ice.harvest.AwsCandidateHarvester, face=null, mask=null
2021-01-21 18:44:02.155 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=753ms).  stunDiscoveryFailed=false
2021-01-21 18:44:02.465 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. 
2021-01-21 18:44:02.466 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. 
2021-01-21 18:44:02.868 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@c81fd12{/,null,AVAILABLE}
2021-01-21 18:44:02.879 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@302f7971{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
2021-01-21 18:44:02.879 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @1896ms
2021-01-21 18:44:11.815 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0.001S. Sticky failure: false
2021-01-21 18:44:21.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:44:31.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:44:41.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:44:51.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:01.716 INFO: [15] VideobridgeExpireThread.expire#140: Running expire()
2021-01-21 18:45:01.815 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:11.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:21.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:31.815 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:41.815 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:45:51.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:01.716 INFO: [15] VideobridgeExpireThread.expire#140: Running expire()
2021-01-21 18:46:01.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:11.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:21.815 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:31.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:41.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 18:46:51.814 INFO: [16] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false

still no log file

xmpp

JVB starts to listen UDP/10000 after the first room created

oh, yes, xmpp.

I have changed the parameter, still no effect.

/usr/share/jitsi-videobridge/jvb.sh --host=localhost --domain=meet.domain.de --port=5347 --secret=12345 --apis=xmpp,

2021-01-21 19:24:55.676 INFO: [1] JitsiConfig.<clinit>#47: Initialized newConfig: merge of 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-1.0-214-gfc6cda2.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/ice4j-3.0-22-g67ffceb.jar!/reference.conf: 1
2021-01-21 19:24:55.681 INFO: [1] ReadOnlyConfigurationService.reloadConfiguration#40: net.java.sip.communicator.SC_HOME_DIR_LOCATION not set
2021-01-21 19:24:55.681 INFO: [1] JitsiConfig.<clinit>#68: Initialized legacyConfig: sip communicator props (no description provided)
2021-01-21 19:24:55.683 INFO: [1] JitsiConfig$Companion.reloadNewConfig#94: Reloading the Typesafe config source (previously reloaded 0 times).
2021-01-21 19:24:55.929 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using AwsCandidateHarvester.
2021-01-21 19:24:55.991 INFO: [1] LastNReducer.<init>#65: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 0 maxEnforcedLastN: 40
2021-01-21 19:24:55.993 INFO: [1] TaskPools.<clinit>#81: TaskPools detected 4 processors, creating the CPU pool with that many threads
2021-01-21 19:24:56.009 INFO: [1] UlimitCheck.printUlimits#115: Running with open files limit 524288 (hard 524288), thread limit 63934 (hard 63934).
2021-01-21 19:24:56.011 INFO: [1] VideobridgeExpireThread.start#88: Starting with 60 second interval.
2021-01-21 19:24:56.104 INFO: [1] HealthChecker.start#118: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
2021-01-21 19:24:56.107 WARNING: [1] MainKt.main#91: Statistics are not enabled, publishing updated presence will not work.
2021-01-21 19:24:56.109 INFO: [1] MainKt.main#110: Not starting CallstatsService, disabled in configuration.
2021-01-21 19:24:56.112 INFO: [1] MainKt.main#128: Not starting public http server
2021-01-21 19:24:56.113 INFO: [1] MainKt.main#137: Starting private http server
2021-01-21 19:24:56.165 INFO: [1] org.eclipse.jetty.util.log.Log.initialized: Logging initialized @867ms to org.eclipse.jetty.util.log.JavaUtilLog
2021-01-21 19:24:56.237 INFO: [1] org.eclipse.jetty.server.Server.doStart: jetty-9.4.35.v20201120; built: 2020-11-20T21:17:03.964Z; git: bdc54f03a5e0a7e280fab27f55c3c75ee8da89fb; jvm 1.8.0_275-b01
2021-01-21 19:24:56.450 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.maybeAdd: Discarding a mapping harvester: org.ice4j.ice.harvest.AwsCandidateHarvester, face=null, mask=null
2021-01-21 19:24:56.451 INFO: [11] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=749ms).  stunDiscoveryFailed=false
2021-01-21 19:24:56.744 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. 
2021-01-21 19:24:56.745 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. 
2021-01-21 19:24:57.079 INFO: [1] org.eclipse.jetty.server.handler.ContextHandler.doStart: Started o.e.j.s.ServletContextHandler@5f13be1{/,null,AVAILABLE}
2021-01-21 19:24:57.090 INFO: [1] org.eclipse.jetty.server.AbstractConnector.doStart: Started ServerConnector@282cb7c7{HTTP/1.1, (http/1.1)}{127.0.0.1:8080}
2021-01-21 19:24:57.091 INFO: [1] org.eclipse.jetty.server.Server.doStart: Started @1794ms
2021-01-21 19:25:06.104 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0.001S. Sticky failure: false
2021-01-21 19:25:16.104 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 19:25:26.104 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 19:25:36.103 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 19:25:46.103 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 19:25:56.012 INFO: [14] VideobridgeExpireThread.expire#140: Running expire()
2021-01-21 19:25:56.103 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false
2021-01-21 19:26:06.104 INFO: [15] HealthChecker.run#171: Performed a successful health check in PT0S. Sticky failure: false

well, it could be much more interesting to use parameter “a” rather than “l” for your netstat. It’s not sure that jvb has connected to prosody (if chat works it means that jicofo has) - I prefer to use ss -tapnu.
Also the prosody log, config.js and prosody config file could be useful.
Or you can validate the telnet interface in prosody (add admin_telnet module in the host) and use the following commands after telnetting to localhost port 5582:

host:list() -> configured hosts
c2s:show() -> connected clients: there should be 2, jvb and focus (jicofo)
port:list() -> listening ports

config.js

var config = { 
    hosts: {
        domain: 'meet.domain.de',
        bridge: 'jitsi-videobridge.domain.de',
        focus:  'focus.meet.domain.de',
        muc:    'conference.meet.domain.de'
    },  
 
    useNicks: false,
    bosh: '//meet.domain.de/http-bind',
 
    clientNode: 'http://jitsi.org/jitsimeet',
 
    testing: {
        p2pTestMode: false
    },  
 
    enableNoAudioDetection: true,
    enableNoisyMicDetection: true,
    channelLastN: -1, 
    enableWelcomePage: true,
 
    p2p: {
        enabled: true,
        stunServers: [
            { urls: 'stun:meet-jit-si-turnrelay.jitsi.net:443' }
        ]   
    },  
 
    analytics: {
    },  
 
    deploymentInfo: {
    },  
 
    makeJsonParserHappy: 'even if last key had a trailing comma'
};

prosody.cfg.loa

prosody.log (systemd)

ss -tapnu

Netid    State        Recv-Q    Send-Q                Local Address:Port                Peer Address:Port     Process
udp      UNCONN       0         0                                 *:13791                          *:*         users:(("java",pid=206,fd=134))
tcp      LISTEN       0         128                         0.0.0.0:5269                     0.0.0.0:*         users:(("lua5.2",pid=165,fd=5))
tcp      LISTEN       0         128                         0.0.0.0:22                       0.0.0.0:*         users:(("sshd",pid=34,fd=3))
tcp      LISTEN       0         128                         0.0.0.0:5280                     0.0.0.0:*         users:(("lua5.2",pid=165,fd=7))
tcp      LISTEN       0         128                       127.0.0.1:5347                     0.0.0.0:*         users:(("lua5.2",pid=165,fd=13))
tcp      LISTEN       0         128                         0.0.0.0:5222                     0.0.0.0:*         users:(("lua5.2",pid=165,fd=11))
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41930
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41938
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41940
tcp      ESTAB        0         0                         127.0.0.1:5347                   127.0.0.1:34336     users:(("lua5.2",pid=165,fd=16))
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41918
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41926
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41932
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41924
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41914
tcp      TIME-WAIT    0         0                         127.0.0.1:5222                   127.0.0.1:41916
tcp      ESTAB        0         44                    xxx.xxx.xxx.xxx:22                    yyy.yyy.yyy.yyy:39156     users:(("sshd",pid=124,fd=4),("sshd",pid=114,fd=4))
tcp      LISTEN       0         128                            [::]:5269                        [::]:*         users:(("lua5.2",pid=165,fd=6))
tcp      LISTEN       0         128                            [::]:22                          [::]:*         users:(("sshd",pid=34,fd=4))
tcp      LISTEN       0         50                                *:8888                           *:*         users:(("java",pid=206,fd=142))
tcp      LISTEN       0         511                               *:443                            *:*         users:(("httpd",pid=357,fd=6),("httpd",pid=253,fd=6),("httpd",pid=252,fd=6),("httpd",pid=251,fd=6),("httpd",pid=250,fd=6))
tcp      LISTEN       0         128                            [::]:5280                        [::]:*         users:(("lua5.2",pid=165,fd=8))
tcp      LISTEN       0         128                           [::1]:5347                        [::]:*         users:(("lua5.2",pid=165,fd=14))
tcp      LISTEN       0         128                            [::]:5222                        [::]:*         users:(("lua5.2",pid=165,fd=12))
tcp      LISTEN       0         511                               *:80                             *:*         users:(("httpd",pid=357,fd=4),("httpd",pid=253,fd=4),("httpd",pid=252,fd=4),("httpd",pid=251,fd=4),("httpd",pid=250,fd=4))
tcp      LISTEN       0         50               [::ffff:127.0.0.1]:8080                           *:*         users:(("java",pid=168,fd=146))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45522
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49628
tcp      ESTAB        0         0                             [::1]:41114                      [::1]:5280      users:(("httpd",pid=253,fd=22))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49630
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49634
tcp      ESTAB        0         0                             [::1]:41102                      [::1]:5280      users:(("httpd",pid=357,fd=19))
tcp      ESTAB        0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45558     users:(("httpd",pid=357,fd=22))
tcp      ESTAB        0         0                             [::1]:5280                       [::1]:41096     users:(("lua5.2",pid=165,fd=15))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45524
tcp      ESTAB        0         0                             [::1]:41128                      [::1]:5280      users:(("httpd",pid=357,fd=21))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45530
tcp      ESTAB        0         0                             [::1]:5280                       [::1]:41114     users:(("lua5.2",pid=165,fd=19))
tcp      ESTAB        0         0                             [::1]:41096                      [::1]:5280      users:(("httpd",pid=251,fd=19))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45550
tcp      ESTAB        0         0                             [::1]:41106                      [::1]:5280      users:(("httpd",pid=253,fd=19))
tcp      ESTAB        0         0                             [::1]:5280                       [::1]:41102     users:(("lua5.2",pid=165,fd=17))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45528
tcp      ESTAB        0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49640     users:(("httpd",pid=251,fd=18))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45554
tcp      ESTAB        0         0                             [::1]:5280                       [::1]:41128     users:(("lua5.2",pid=165,fd=20))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45552
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45526
tcp      ESTAB        0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49638     users:(("httpd",pid=357,fd=18))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:49636
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45548
tcp      ESTAB        0         0                [::ffff:127.0.0.1]:34336         [::ffff:127.0.0.1]:5347      users:(("java",pid=206,fd=147))
tcp      TIME-WAIT    0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45520
tcp      ESTAB        0         0            [::ffff:xxx.xxx.xxx.xxx]:443          [::ffff:yyy.yyy.yyy.yyy]:45556     users:(("httpd",pid=357,fd=20))
tcp      ESTAB        0         0                             [::1]:5280                       [::1]:41106     users:(("lua5.2",pid=165,fd=18))

It’s quite clear that jvb can’t connect to prosody (the repeated read error occurrences).
Also you have 2 java processes, 206 and 168; 206 is listening on 8888 and also connecting on port 5347 (that’s Jicofo, at least the version of a few weeks ago) and as an established connection while 168 is only listening. If you were using mod_admin_telnet you’d see that only jicofo is connected. That the errors happen just after the tls handshake suggest a possible certificate problem.
Try to set in the sip-communicator.properties the following workaround:
org.jitsi.videobridge.xmpp.user.shard.DISABLE_CERTIFICATE_VERIFICATION=true
it’s not the most elegant fix but it could help to go further or at least confirm that this is not a certificate problem in fact.

I change my

/etc/jitsi/videobridge/sip-communicator.properties

org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.meet.wandel-network.de/.*
org.jitsi.impl.neomedia.transform.srtp.SRTPCryptoContext.checkReplay=false
org.jitsi.videobridge.xmpp.user.shard.DISABLE_CERTIFICATE_VERIFICATION=true

Same problem, still no video. I don’t think this is a certificate Problem. I have a RapidSSL Wildcard certificate for all subdomains.

Your jvb is missing the configuration for the brewery room.

Without bridges you should be seeing errors in the js console saying no bridge available and follows a reload of the page.

Thank you very much! I think this was my primary problem.

But now the server crashes and i get an error

org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error reply received from internal.auth.meet.domain.de: XMPPError: remote-server-not-found - cancel. Generated by a
uth.domain.de

You need those virtualhosts created in prosody

yes, this entry (at least) is missing

Component "internal.auth.domain.com" "muc"
    storage = "memory"
    modules_enabled = {
      "ping";
      "muc_domain_mapper";
    }
    admins = { "focus@auth.domain.com", "jvb@auth.domain.com" }
    muc_room_locking = false
    muc_room_default_public_jids = true

Thank you both! It works now. :slight_smile: