No audio and video

Hello everyone, I had a problem with my jitsi server in the audio and video, when starting a meeting it does not play the video and audio.

thanks and regards,
Camilo A. Pimentel G.

Any errors in the console? Maybe share the js console logs.

@damencho how can I show you the logs errors?

Tools - developer menu - console logs … Something like that …

@damencho

LocalStatsCollector.js:22 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu

||(anonymous)|@|LocalStatsCollector.js:22|
| --- | --- | --- | --- |
||n|@|bootstrap:19|
||(anonymous)|@|statistics.js:1|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:1|
||n|@|bootstrap:19|
||(anonymous)|@|JitsiConferenceEventManager.js:1|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:10|
||n|@|bootstrap:19|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:10|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:10|
||n|@|bootstrap:19|
||(anonymous)|@|JitsiConnection.js:1|
||n|@|bootstrap:19|
||(anonymous)|@|JitsiMeetJS.js:1|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:17|
||n|@|bootstrap:19|
||(anonymous)|@|index.js:3|
||n|@|bootstrap:19|
||(anonymous)|@|bootstrap:83|
||(anonymous)|@|lib-jitsi-meet.min.js?v=4628:1|
||(anonymous)|@|universalModuleDefinition:9|
||(anonymous)|@|universalModuleDefinition:1|

2021-02-09T02:49:54.490Z [modules/UI/videolayout/VideoLayout.js] <Object.changeUserAvatar>: Missed avatar update - no small video yet for undefined

||o|@|Logger.js:154|
| --- | --- | --- | --- |
||changeUserAvatar|@|VideoLayout.js:485|
||k.refreshAvatarDisplay|@|UI.js:385|
||Qt|@|middleware.js:427|
||(anonymous)|@|middleware.js:136|
||(anonymous)|@|middleware.js:21|
||(anonymous)|@|middleware.js:60|
||(anonymous)|@|middleware.js:44|
||(anonymous)|@|middleware.js:49|
||(anonymous)|@|middleware.js:28|
||(anonymous)|@|middleware.js:12|
||(anonymous)|@|middleware.js:39|
||(anonymous)|@|middleware.js:31|
||(anonymous)|@|middleware.web.js:22|
||(anonymous)|@|middleware.any.js:100|
||(anonymous)|@|middleware.js:106|
||(anonymous)|@|middleware.js:19|
||(anonymous)|@|middleware.js:29|
||(anonymous)|@|middleware.js:91|
||(anonymous)|@|middleware.js:101|
||(anonymous)|@|middleware.js:24|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:15|
||(anonymous)|@|middleware.js:23|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:25|
||(anonymous)|@|middleware.js:74|
||(anonymous)|@|middleware.js:40|
||(anonymous)|@|middleware.js:158|
||dispatch|@|redux.js:636|
||Promise.then (async)|||
||componentDidMount|@|BaseApp.js:87|
||componentDidMount|@|AbstractApp.js:42|
||js|@|react-dom.production.min.js:238|
||t.unstable_runWithPriority|@|scheduler.production.min.js:20|
||pa|@|react-dom.production.min.js:113|
||Es|@|react-dom.production.min.js:230|
||ds|@|react-dom.production.min.js:204|
||Vs|@|react-dom.production.min.js:263|
||Ws|@|react-dom.production.min.js:263|
||(anonymous)|@|react-dom.production.min.js:272|
||ys|@|react-dom.production.min.js:208|
||el|@|react-dom.production.min.js:272|
||render|@|react-dom.production.min.js:273|
||Rs.renderEntryPoint|@|index.web.js:71|
||(anonymous)|@|(index):25|
||Show 93 more frames|

2021-02-09T02:49:54.503Z [modules/statistics/AnalyticsAdapter.js] <Object.dispose>: Disposing of analytics adapter.

||o|@|Logger.js:154|
| --- | --- | --- | --- |
||dispose|@|AnalyticsAdapter.js:116|
||v|@|functions.js:141|
||(anonymous)|@|middleware.js:95|
||(anonymous)|@|middleware.js:19|
||(anonymous)|@|middleware.js:29|
||(anonymous)|@|middleware.js:91|
||(anonymous)|@|middleware.js:101|
||(anonymous)|@|middleware.js:24|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:15|
||(anonymous)|@|middleware.js:23|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:25|
||(anonymous)|@|middleware.js:74|
||(anonymous)|@|middleware.js:40|
||(anonymous)|@|middleware.js:158|
||dispatch|@|redux.js:636|
||(anonymous)|@|actions.js:138|
||async function (async)|||
||(anonymous)|@|actions.js:111|
||(anonymous)|@|index.js:11|
||(anonymous)|@|middleware.js:29|
||(anonymous)|@|middleware.js:32|
||(anonymous)|@|middleware.js:31|
||(anonymous)|@|middleware.web.js:33|
||(anonymous)|@|middleware.any.js:22|
||(anonymous)|@|middleware.js:67|
||(anonymous)|@|middleware.js:43|
||(anonymous)|@|middleware.js:61|
||(anonymous)|@|middleware.js:79|
||Promise.then (async)|||
||componentDidMount|@|AbstractApp.js:44|
||js|@|react-dom.production.min.js:238|
||t.unstable_runWithPriority|@|scheduler.production.min.js:20|
||pa|@|react-dom.production.min.js:113|
||Es|@|react-dom.production.min.js:230|
||ds|@|react-dom.production.min.js:204|
||Vs|@|react-dom.production.min.js:263|
||Ws|@|react-dom.production.min.js:263|
||(anonymous)|@|react-dom.production.min.js:272|
||ys|@|react-dom.production.min.js:208|
||el|@|react-dom.production.min.js:272|
||render|@|react-dom.production.min.js:273|
||Rs.renderEntryPoint|@|index.web.js:71|
||(anonymous)|@|(index):25|
||Show 53 more frames|
2021-02-09T02:49:54.503Z [modules/statistics/AnalyticsAdapter.js] <Object.dispose>: Disposing of analytics adapter.

||o|@|Logger.js:154|
| --- | --- | --- | --- |
||dispose|@|AnalyticsAdapter.js:116|
||v|@|functions.js:141|
||(anonymous)|@|middleware.js:95|
||(anonymous)|@|middleware.js:19|
||(anonymous)|@|middleware.js:29|
||(anonymous)|@|middleware.js:91|
||(anonymous)|@|middleware.js:101|
||(anonymous)|@|middleware.js:24|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:15|
||(anonymous)|@|middleware.js:23|
||(anonymous)|@|middleware.js:20|
||(anonymous)|@|middleware.js:25|
||(anonymous)|@|middleware.js:74|
||(anonymous)|@|middleware.js:40|
||(anonymous)|@|middleware.js:158|
||dispatch|@|redux.js:636|
||(anonymous)|@|actions.js:138|
||async function (async)|||
||(anonymous)|@|actions.js:111|
||(anonymous)|@|index.js:11|
||(anonymous)|@|middleware.js:29|
||(anonymous)|@|middleware.js:32|
||(anonymous)|@|middleware.js:31|
||(anonymous)|@|middleware.web.js:33|
||(anonymous)|@|middleware.any.js:22|
||(anonymous)|@|middleware.js:67|
||(anonymous)|@|middleware.js:43|
||(anonymous)|@|middleware.js:61|
||(anonymous)|@|middleware.js:79|
||Promise.then (async)|||
||componentDidMount|@|AbstractApp.js:44|
||js|@|react-dom.production.min.js:238|
||t.unstable_runWithPriority|@|scheduler.production.min.js:20|
||pa|@|react-dom.production.min.js:113|
||Es|@|react-dom.production.min.js:230|
||ds|@|react-dom.production.min.js:204|
||Vs|@|react-dom.production.min.js:263|
||Ws|@|react-dom.production.min.js:263|
||(anonymous)|@|react-dom.production.min.js:272|
||ys|@|react-dom.production.min.js:208|
||el|@|react-dom.production.min.js:272|
||render|@|react-dom.production.min.js:273|
||Rs.renderEntryPoint|@|index.web.js:71|
||(anonymous)|@|(index):25|
||Show 53 more frames|

What is the complete log when you enter a room?

@damencho

Logger.js:154 2021-02-09T03:48:10.222Z [features/base/tracks] Failed to create local tracks

1. (2) ["audio", "video"]

1. s {gum: {…}, name: "gum.not_found", message: "Requested device(s) was/were not found: audio, video", stack: "Error↵ at new s (https://voffic-meet.com/libs/l…eet.com/libs/lib-jitsi-meet.min.js?v=4628:1:93436"}

  1. gum: {error: DOMException: Requested device not found, constraints: {…}, devices: Array(2)}
  2. message: "Requested device(s) was/were not found: audio, video"
  3. name: "gum.not_found"
  4. stack: "Error↵ at new s (https://voffic-meet.com/libs/lib-jitsi-meet.min.js?v=4628:1:118591)↵ at https://voffic-meet.com/libs/lib-jitsi-meet.min.js?v=4628:1:93436"
  5. __proto__: Error

Logger.js:154 2021-02-09T04:03:06.518Z [features/base/tracks] Failed to create local tracks (2) ["audio", "video"]0: "audio"1: "video"length: 2__proto__: Array(0) s {gum: {…}, name: "gum.not_found", message: "Requested device(s) was/were not found: audio, video", stack: "Error↵ at new s (https://voffic-meet.com/libs/l…eet.com/libs/lib-jitsi-meet.min.js?v=4628:1:93436"}

I don’t see jicofo joining the room, you better check jicofo logs.

@damencho
How can I check the jocofono records?

in /var/log/jitsi/jicofo.log

@damencho hello, I share the file for a better analysis of the problem.

Thank you very much and greetings

Looks like your prosody server is not running at all.
ps ax | grep lua?
You can check prosody logs in /var/log/prosody.

@damencho I updated the Prosody and it started crashing, reinstalled the jitsi using this guide.

thanks and regards

|Feb 09 01:54:59 general|info|Hello and welcome to Prosody version 0.10.0|
|---|---|---|
|Feb 09 01:54:59 general|info|Prosody is using the select backend for connection handling|
|Feb 09 01:54:59 portmanager|info|Activated service 's2s' on [::]:5269, [*]:5269|
|Feb 09 01:54:59 portmanager|info|Activated service 'c2s' on [::]:5222, [*]:5222|
|Feb 09 01:54:59 portmanager|info|Activated service 'legacy_ssl' on no ports|
|Feb 09 01:54:59 mod_posix|info|Prosody is about to detach from the console, disabling further console output|
|Feb 09 01:54:59 mod_posix|info|Successfully daemonized to PID 4732|
|Feb 09 01:55:03 mod_posix|warn|Received SIGTERM|
|Feb 09 01:55:03 general|info|Shutting down: Received SIGTERM|
|Feb 09 01:55:03 general|info|Shutting down...|
|Feb 09 01:55:03 general|info|Shutdown status: Cleaning up|
|Feb 09 01:55:03 general|info|Shutdown complete|
|Feb 09 01:55:03 general|info|Hello and welcome to Prosody version 0.10.0|
|Feb 09 01:55:03 general|info|Prosody is using the select backend for connection handling|
|Feb 09 01:55:03 speakerstats.voffic-meet.com:speakerstats_component|warn|speaker stats will not work with Prosody version 0.10 or less.|
|Feb 09 01:55:03 portmanager|info|Activated service 's2s' on [::]:5269, [*]:5269|
|Feb 09 01:55:03 portmanager|info|Activated service 'c2s' on [::]:5222, [*]:5222|
|Feb 09 01:55:03 portmanager|info|Activated service 'legacy_ssl' on no ports|
|Feb 09 01:55:03 mod_posix|info|Prosody is about to detach from the console, disabling further console output|
|Feb 09 01:55:03 mod_posix|info|Successfully daemonized to PID 6231|
|Feb 09 01:55:03 voffic-meet.com:muc_lobby_rooms|warn|Lobby rooms will not work with Prosody version 0.10 or less.|
|Feb 09 01:55:03 portmanager|info|Activated service 'http' on [::]:5280, [*]:5280|
|Feb 09 01:55:03 portmanager|error|Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281|
|Feb 09 01:55:03 portmanager|error|Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281|
|Feb 09 01:55:03 portmanager|info|Activated service 'https' on no ports|
|Feb 09 01:55:03 conferenceduration.voffic-meet.com:conference_duration_component|warn|conference duration will not work with Prosody version 0.10 or less.|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host speakerstats.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host conferenceduration.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host internal.auth.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host auth.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host conference.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host lobby.voffic-meet.com!|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host localhost!|
|Feb 09 01:55:03 portmanager|info|Activated service 'component' on [127.0.0.1]:5347, [::1]:5347|
|Feb 09 01:55:03 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host focus.voffic-meet.com!|
|Feb 09 02:08:26 mod_posix|warn|Received SIGTERM|
|Feb 09 02:08:26 general|info|Shutting down: Received SIGTERM|
|Feb 09 02:08:26 general|info|Shutting down...|
|Feb 09 02:08:26 general|info|Shutdown status: Cleaning up|
|Feb 09 02:08:26 general|info|Shutdown complete|
|Feb 09 02:08:26 general|info|Hello and welcome to Prosody version 0.10.0|
|Feb 09 02:08:26 general|info|Prosody is using the select backend for connection handling|
|Feb 09 02:08:26 speakerstats.voffic-meet.com:speakerstats_component|warn|speaker stats will not work with Prosody version 0.10 or less.|
|Feb 09 02:08:26 portmanager|info|Activated service 's2s' on [::]:5269, [*]:5269|
|Feb 09 02:08:26 portmanager|info|Activated service 'c2s' on [::]:5222, [*]:5222|
|Feb 09 02:08:26 portmanager|info|Activated service 'legacy_ssl' on no ports|
|Feb 09 02:08:26 mod_posix|info|Prosody is about to detach from the console, disabling further console output|
|Feb 09 02:08:26 mod_posix|info|Successfully daemonized to PID 19652|
|Feb 09 02:08:26 guest.voffic-meet.com:muc_lobby_rooms|warn|Lobby rooms will not work with Prosody version 0.10 or less.|
|Feb 09 02:08:26 portmanager|info|Activated service 'http' on [::]:5280, [*]:5280|
|Feb 09 02:08:26 portmanager|error|Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281|
|Feb 09 02:08:26 portmanager|error|Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281|
|Feb 09 02:08:26 portmanager|info|Activated service 'https' on no ports|
|Feb 09 02:08:26 conferenceduration.voffic-meet.com:conference_duration_component|warn|conference duration will not work with Prosody version 0.10 or less.|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host speakerstats.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host conference.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host lobby.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host internal.auth.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host auth.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host conferenceduration.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host guest.voffic-meet.com!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host localhost!|
|Feb 09 02:08:26 conference.voffic-meet.com:muc_domain_mapper|info|Loading mod_muc_domain_mapper for host focus.voffic-meet.com!|
|Feb 09 02:08:26 portmanager|info|Activated service 'component' on [127.0.0.1]:5347, [::1]:5347|

What does start crashing mean? On what is jicofo now able to connect?

@damencho Hi, Fail… it started to fail since the prosydi update. then, i reinstalled jitsi on the server and i have the same problem (new private server)

I don’t understand, because you ask where you can connect jicofo?

regards