No connections after Debian 9 to 10 upgrade

Hello,

I had a working Jisti-meet installation on a Debian 9 system.

Since I upgraded to Debian 10 it doesn’t work anymore and I can’t understand why.

The effect is that if I connect from two different PCs I can’t see the respective other connection.

Then also webcam doesn’t show anything, even if it can see it’s working from the “Settings” menu.

From logs I can’t see any “GRAVE” line.

Any idea?

Matteo

Can you check the java version and make sure default is java8?

Yes, it is:

  Selezione    Percorso                                        Priorità  Stato
------------------------------------------------------------
  0            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      modalità automatica
  1            /usr/lib/jvm/java-11-openjdk-amd64/bin/java      1111      modalità manuale
* 2            /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java   1081      modalità manuale

As a start maybe check browser logs, do you see any errors there? If that is ok, check prosody and jicofo logs. Check whether your bosh is working by checking its url, should looks like https://meet.jit.si/http-bind

Thanks, here are browser logs:

Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead  jquery-1.10.2.min.js:1
(TIME) index.html loaded:	 118  ORSTest:18:9
[modules/browser/BrowserCapabilities.js] <t>:  This appears to be firefox, ver: 60.0  lib-jitsi-meet.min.js:6:249370
[react/index.web.js] <>:  (TIME) document ready:	 943  app.bundle.min.js:60:73810
[react/features/base/storage/PersistenceRegistry.js] <getPersistedState>:  redux state rehydrated as <unavailable>  app.bundle.min.js:60:73810
[modules/UI/videolayout/VideoLayout.js] <changeUserAvatar>:  Missed avatar update - no small video yet for undefined  app.bundle.min.js:60:73810
[react/features/base/media/middleware.js] <>:  Start muted:   app.bundle.min.js:60:73810
[react/features/base/media/middleware.js] <>:  Start audio only set to false  app.bundle.min.js:60:73810
[react/features/base/conference/middleware.js] <>:  Audio-only disabled  app.bundle.min.js:60:73810
[react/features/analytics/functions.js] <u/</<>:  Error creating analytics handler: Error: Failed to initialize Amplitude handler, no APP key  app.bundle.min.js:60:73810
[react/features/analytics/functions.js] <u/</<>:  Loaded 0 analytics handlers  app.bundle.min.js:60:73810
[react/features/base/devices/actions.js] <l/</</<>:  Failed to set audio output device.
                        Default audio output device will be used instead Error: Audio output device change is not supported  app.bundle.min.js:60:73810
[modules/RTC/RTCUtils.js] <value/<>:  Available devices:  <unavailable>  lib-jitsi-meet.min.js:6:249370
[conference.js] <updateAudioIconEnabled>:  Microphone button enabled: true local audio: null audio devices: [object MediaDeviceInfo],[object MediaDeviceInfo],[object MediaDeviceInfo] device count: 3  app.bundle.min.js:60:73810
[conference.js] <updateVideoIconEnabled>:  Camera button enabled: true local video: null video devices: [object MediaDeviceInfo],[object MediaDeviceInfo] device count: 2  app.bundle.min.js:60:73810
[modules/xmpp/xmpp.js] <value>:  P2P STUN servers:  <unavailable>  lib-jitsi-meet.min.js:6:249370
[modules/xmpp/xmpp.js] <value>:  (TIME) Strophe connecting:	 1681  lib-jitsi-meet.min.js:6:249370
[modules/RTC/RTCUtils.js] <value>:  Using the new gUM flow  lib-jitsi-meet.min.js:6:249370
[modules/RTC/RTCUtils.js] <value/i<>:  Got media constraints:  <unavailable>  lib-jitsi-meet.min.js:6:249370
[modules/xmpp/strophe.util.js] <t.a/i.Strophe.log>:  Strophe: Server did not yet offer a supported authentication mechanism. Sending a blank poll request.  lib-jitsi-meet.min.js:6:249370
[modules/RTC/RTCUtils.js] <value/</<>:  onUserMediaSuccess  lib-jitsi-meet.min.js:6:249370
[modules/RTC/JitsiLocalTrack.js] <value>:  Setting new MSID: {045dcacc-7934-42c5-a979-79cd8ac2f5ea} {9c53b5b5-80db-4540-acc3-bb585bf14097} on LocalTrack[undefined,audio]  lib-jitsi-meet.min.js:6:249370
[modules/RTC/JitsiLocalTrack.js] <value>:  Setting new MSID: {80f9bb60-203d-4891-a783-349b3c4d707b} {c720dea8-3a1b-49bd-8d63-a5797107c9a4} on LocalTrack[undefined,video]  lib-jitsi-meet.min.js:6:249370
[react/features/base/storage/PersistenceRegistry.js] <persistState>:  redux state persisted. 1a2069f9b84a68b790e4f3b5d77b2d6d -> a01877dbec8f749817a31e506cbf6f9d  app.bundle.min.js:60:73810
[JitsiMeetJS.js] <getGlobalOnErrorHandler>:  UnhandledError: null Script: null Line: null Column: null StackTrace:  <unavailable>  lib-jitsi-meet.min.js:6:249370
[modules/xmpp/strophe.util.js] <t.a/i.Strophe.log>:  Strophe: request id 2.1 error 504 happened  lib-jitsi-meet.min.js:6:249370
[modules/xmpp/strophe.util.js] <t.a/i.Strophe.log>:  Strophe: request errored, status: 504, number of errors: 1  lib-jitsi-meet.min.js:6:249370
[modules/xmpp/strophe.util.js] <t.a/i.Strophe.log>:  Strophe: Server did not yet offer a supported authentication mechanism. Sending a blank poll request.  lib-jitsi-meet.min.js:6:249370

Bosh:

It works! Now point your BOSH client to this URL to connect to Prosody.

For more information see [Prosody: Setting up BOSH](https://prosody.im/doc/setting_up_bosh).

This is suspicious. Check prosody logs for errors, what is the version of prosody you use? What is your prosody config?

Hi,

I have Prosody 0.11.2-1 and in effect I have these errors in is logs:

Aug 01 15:59:21 portmanager     error   Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
Aug 01 15:59:21 portmanager     error   Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

This is my configuration:

root@lxconf01:/etc/prosody# grep "^[^--]" prosody.cfg.lua 
admins = { }
plugin_paths = { "/usr/local/lib/prosody/modules" }
modules_enabled = {
        -- Generally required
                "roster"; -- Allow users to have a roster. Recommended ;)
                "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
                "tls"; -- Add support for secure TLS on c2s/s2s connections
                "dialback"; -- s2s dialback support
                "disco"; -- Service discovery
        -- Not essential, but recommended
                "carbons"; -- Keep multiple clients in sync
                "pep"; -- Enables users to publish their avatar, mood, activity, playing music and more
                "private"; -- Private XML storage (for room bookmarks, etc.)
                "blocklist"; -- Allow users to block communications with other users
                "vcard4"; -- User profiles (stored in PEP)
                "vcard_legacy"; -- Conversion between legacy vCard and PEP Avatar, vcard
        -- Nice to have
                "version"; -- Replies to server version requests
                "uptime"; -- Report how long server has been running
                "time"; -- Let others know the time here on this server
                "ping"; -- Replies to XMPP pings with pongs
                "register"; -- Allow users to register on this server using a client and change passwords
                --"mam"; -- Store messages in an archive and allow users to access it
                --"csi_simple"; -- Simple Mobile optimizations
        -- Admin interfaces
                "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
                --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
        -- HTTP modules
                --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
                --"websocket"; -- XMPP over WebSockets
                --"http_files"; -- Serve static files from a directory over HTTP
        -- Other specific functionality
                "posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
                --"limits"; -- Enable bandwidth limiting for XMPP connections
                --"groups"; -- Shared roster support
                --"server_contact_info"; -- Publish contact information for this service
                --"announce"; -- Send announcement to all online users
                --"welcome"; -- Welcome users who register accounts
                --"watchregistrations"; -- Alert admins of registrations
                --"motd"; -- Send a message to users when they log in
                --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
                --"proxy65"; -- Enables a file transfer proxy service which clients behind NAT can use
}
modules_disabled = {
        -- "offline"; -- Store offline messages
        -- "c2s"; -- Handle client connections
        -- "s2s"; -- Handle server-to-server connections
}
allow_registration = false
daemonize = false;
pidfile = "/run/prosody/prosody.pid";
c2s_require_encryption = true
s2s_require_encryption = true
s2s_secure_auth = false
authentication = "internal_hashed"
archive_expires_after = "1w" -- Remove archived messages after 1 week
log = {
        -- Log files (change 'info' to 'debug' for debug logs):
        info = "/var/log/prosody/prosody.log";
        error = "/var/log/prosody/prosody.err";
        -- Syslog:
        { levels = { "error" }; to = "syslog";  };
}
certificates = "certs"
VirtualHost "conference.x.y"
Include "conf.d/*.cfg.lua"

Here is missing the jitsi-meet configs, but if you are using prosody-0.11 then make sure you have the following setting for your muc: instead of storage = "null" to be storage = "memory".
Is this like that?

Thanks, I tried, but changing like that seems to have no different effect:

--storage = "sql" -- Default is "internal" (Debian: "sql" requires one of the
-- lua-dbi-sqlite3, lua-dbi-mysql or lua-dbi-postgresql packages to work)
storage = "memory"

Here is my jitsi-meet config:

var config = {
hosts: {
domain: ‘conference.x.y’,
anonymousdomain: ‘guest.conference.x.y’,
muc: ‘conference.conference.x.y’, // FIXME: use XEP-0030
bridge: ‘jitsi-videobridge.conference.x.y’, // FIXME: use XEP-0030
//jirecon: ‘jirecon.conference.x.y’,
call_control: ‘callcontrol.conference.x.y’
//focus: ‘focus.conference.x.y’ - defaults to ‘focus.conference.x.y’
},
useNicks: false,
bosh: ‘//conference.x.y/http-bind’, // FIXME: use xep-0156 for that
clientNode: ‘http://jitsi.org/jitsimeet’, // The name of client node advertised in XEP-0115 ‘c’ stanza
desktopSharing: ‘ext’, // Desktop sharing method. Can be set to ‘ext’, ‘webrtc’ or false to disable.
chromeExtensionId: ‘bbhgljdpckpmeoncekpllpaljdlpgglg’, // Id of desktop streamer Chrome extension
desktopSharingChromeExtId: ‘bbhgljdpckpmeoncekpllpaljdlpgglg’,
desktopSharingSources: [‘screen’, ‘window’],
minChromeExtVersion: ‘0.1’, // Required version of Chrome extension
openSctp: true, // Toggle to enable/disable SCTP channels
disableStats: false,
disableAudioLevels: false,
channelLastN: -1, // The default value of the channel attribute last-n.
adaptiveLastN: false,
adaptiveSimulcast: false,
useRtcpMux: true, // required for FF support
useBundle: true, // required for FF support
enableRecording: false,
enableWelcomePage: true,
enableSimulcast: false, // blocks FF support
logStats: false, // Enable logging of PeerConnection stats via the focus
};

Hello,

at last I installed a new Jitsi-meet on a new Debian 10 machine and it worked just perfectly.

I think Jitsi team did a great job on installation packages!

Is there a way to list all ongoing calls with some details?

Thanks,
Matteo