Recording issue mod_c2s debug Received invalid XML (syntax error) 41 bytes: OPTIONS / HTTP/1.0 content-length: 0 [0]

Hi all, so maybe it’s the sum of alle help that can be found in here - my recording stuff is not working as expected. ATM - i am stuck in the - “Recording can be started but breaks down after while”. I tried to get through the logfiles - and after setting debug mode for prosody - i just can find this:
mod_c2s debug Received invalid XML (syntax error) 41 bytes: OPTIONS / HTTP/1.0 content-length: 0 [0]

  • what i also found is:
    2022-01-09 17:29:10.864 FEIN: [71] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading ‘isJoined’)
    2022-01-09 17:29:10.865 SCHWERWIEGEND: [71] CallPage.visit#65: Timed out waiting for call page to load

Checked all… pretty sure i did not miss anything… other then i missend something :wink:

It’s the latest jitsi / jibri version:
Ubuntu 20.x LTS
Java 8
→ Conferencing with more than 5+ people working with audio and video

thanks for any help - appreciate it :slightly_smiling_face:

Welcome to the forum.

What are your server specs?

ESXI 6.7 VM
→ 4 Cores → 16 GB Ram

Share your jibri.conf and your jibri log.

                                                                                                                                                                                                                                                                                                                                                                                  22,0-1      Alles
jibri {
  // A unique identifier for this Jibri
  // TODO: eventually this will be required with no default
  id = ""
  // Whether or not Jibri should return to idle state after handling
  // (successfully or unsuccessfully) a request.  A value of 'true'
  // here means that a Jibri will NOT return back to the IDLE state
  // and will need to be restarted in order to be used again.
  single-use-mode = false
  api {
    http {
      external-api-port = 2222
      internal-api-port = 3333
    }
    xmpp {
      // See example_xmpp_envs.conf for an example of what is expected here
      environments = [
              {
                name = "prod environment"
                xmpp-server-hosts = ["conference.racke.org"]
                xmpp-domain = "conference.racke.org"

                control-muc {
                    domain = "internal.auth.conference.racke.org"
                    room-name = "JibriBrewery"
                    nickname = "jibri-nickname"
                }

                control-login {
                    domain = "auth.conference.racke.org"
                    username = "jibri"
                    password = "JPwd"
                }

                call-login {
                    domain = "recorder.conference.racke.org"
                    username = "recorder"
                    password = "RPwd"
                }

                strip-from-room-domain = "conference."
                usage-timeout = 0
                trust-all-xmpp-certs = true
            }]
    }
  }
  recording {
    recordings-directory = "/srv/recordings"
    # TODO: make this an optional param and remove the default
    finalize-script = "/path/to/finalize_recording.sh"
  }
  streaming {
    // A list of regex patterns for allowed RTMP URLs.  The RTMP URL used
    // when starting a stream must match at least one of the patterns in
    // this list.
    rtmp-allow-list = [
      // By default, all services are allowed
      ".*"
    ]
  }
  chrome {
    // The flags which will be passed to chromium when launching
    flags = [
      "--use-fake-ui-for-media-stream",
      "--start-maximized",
      "--kiosk",
      "--enabled",
      "--disable-infobars",
      "--autoplay-policy=no-user-gesture-required"
    ]
  }
  stats {
    enable-stats-d = true
  }
  webhook {
    // A list of subscribers interested in receiving webhook events
    subscribers = []
  }
  jwt-info {
    // The path to a .pem file which will be used to sign JWT tokens used in webhook
    // requests.  If not set, no JWT will be added to webhook requests.
    # signing-key-path = "/path/to/key.pem"

    // The kid to use as part of the JWT
    # kid = "key-id"

    // The issuer of the JWT
    # issuer = "issuer"

    // The audience of the JWT
    # audience = "audience"

    // The TTL of each generated JWT.  Can't be less than 10 minutes.
    # ttl = 1 hour
  }
  call-status-checks {
    // If all clients have their audio and video muted and if Jibri does not
    // detect any data stream (audio or video) comming in, it will stop
    // recording after NO_MEDIA_TIMEOUT expires.
    no-media-timeout = 30 seconds

    // If all clients have their audio and video muted, Jibri consideres this
    // as an empty call and stops the recording after ALL_MUTED_TIMEOUT expires.
    all-muted-timeout = 10 minutes

    // When detecting if a call is empty, Jibri takes into consideration for how
    // long the call has been empty already. If it has been empty for more than
    // DEFAULT_CALL_EMPTY_TIMEOUT, it will consider it empty and stop the recording.
    default-call-empty-timeout = 30 seconds
  }
}

posted the config and here is the relevant part of the jibri.log

2022-01-09 17:29:09.840 FEIN: [71] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-01-09 17:29:10.351 FEIN: [71] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-01-09 17:29:10.864 FEIN: [71] CallPage$visit$$inlined$measureTimedValue$lambda$1.apply#58: Not joined yet: Cannot read properties of undefined (reading 'isJoined')
2022-01-09 17:29:10.865 SCHWERWIEGEND: [71] CallPage.visit#65: Timed out waiting for call page to load
2022-01-09 17:29:10.865 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.onSeleniumStateChange#213: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join th
e call
2022-01-09 17:29:10.865 INFORMATION: [71] [session_id=pemuimbmcawjemsm] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCa
ll SESSION Failed to join the call
2022-01-09 17:29:10.866 INFORMATION: [71] XmppApi$createServiceStatusHandler$1.invoke#243: Current service had an error Error: FailedToJoinCall SESSION Failed to join the call, sending error iq <iq xmln
s='jabber:client' to='jibribrewery@internal.auth.conference.racke.org/focus' id='IXMJM-47' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='tru
e'/></iq>
2022-01-09 17:29:10.867 FEIN: [71] JibriStatsDClient.incrementCounter#38: Incrementing statsd counter: stop:recording
2022-01-09 17:29:10.867 INFORMATION: [71] JibriManager.stopService#260: Stopping the current service
2022-01-09 17:29:10.867 INFORMATION: [71] [session_id=pemuimbmcawjemsm] FileRecordingJibriService.stop#181: Stopping capturer
2022-01-09 17:29:10.868 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSubprocess.stop#75: Stopping ffmpeg process
2022-01-09 17:29:10.868 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSubprocess.stop#89: ffmpeg exited with value null
2022-01-09 17:29:10.868 INFORMATION: [71] [session_id=pemuimbmcawjemsm] FileRecordingJibriService.stop#183: Quitting selenium
2022-01-09 17:29:10.868 INFORMATION: [71] [session_id=pemuimbmcawjemsm] FileRecordingJibriService.stop#190: No media was recorded, deleting directory and skipping metadata file & finalize
2022-01-09 17:29:10.869 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#334: Leaving call and quitting browser
2022-01-09 17:29:10.869 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#337: Recurring call status checks cancelled
2022-01-09 17:29:10.882 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#343: Got 9 log entries for type browser
2022-01-09 17:29:10.946 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#343: Got 999 log entries for type driver
2022-01-09 17:29:11.160 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#343: Got 0 log entries for type client
2022-01-09 17:29:11.160 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#352: Leaving web call
2022-01-09 17:29:11.215 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#359: Quitting chrome driver
2022-01-09 17:29:11.300 INFORMATION: [71] [session_id=pemuimbmcawjemsm] JibriSelenium.leaveCallAndQuitBrowser#361: Chrome driver quit
2022-01-09 17:29:11.300 INFORMATION: [71] JibriStatusManager$$special$$inlined$observable$1.afterChange#72: Busy status has changed: BUSY -> IDLE
2022-01-09 17:29:11.301 FEIN: [71] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status
2022-01-09 17:29:11.301 INFORMATION: [71] XmppApi.updatePresence#144: Jibri reports its status is now JibriStatus(busyStatus=IDLE, health=OverallHealth(healthStatus=HEALTHY, details={})), publishing pre
sence to connections
2022-01-09 17:29:31.469 FEIN: [17] WebhookClient$updateStatus$1.invokeSuspend#107: Updating 0 subscribers of status

jibri.conf looks fine. Can you upload the complete log?
Also, what does your jicofo.conf look like?
And what’s the status of jibri service?

Wait - can you share your prosody config (lua) file as well? Looks like the issue might be there.

Hi Freddie,
here you find the default lua file.
Thanks 4 a helping hand i advance :slight_smile:
KR

-- Prosody Example Configuration File
--
-- Information on configuring Prosody can be found on our
-- website at https://prosody.im/doc/configure
--
-- Tip: You can check that the syntax of this file is correct
-- when you have finished by running this command:
--     prosodyctl check config
-- If there are any errors, it will let you know what and where
-- they are, otherwise it will keep quiet.
--
-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
-- blanks. Good luck, and happy Jabbering!


---------- Server-wide settings ----------
-- Settings in this section apply to the whole server and are the default settings
-- for any virtual hosts

-- This is a (by default, empty) list of accounts that are admins
-- for the server. Note that you must create the accounts separately
-- (see https://prosody.im/doc/creating_accounts for info)
-- Example: admins = { "user1@example.com", "user2@example.net" }
admins = { }

-- Enable use of libevent for better performance under high load
-- For more information see: https://prosody.im/doc/libevent
--use_libevent = true

-- Prosody will always look in its source directory for modules, but
-- this option allows you to specify additional locations where Prosody
-- will look for modules first. For community modules, see https://modules.prosody.im/
-- For a local administrator it's common to place local modifications
-- under /usr/local/ hierarchy:
plugin_paths = { "/usr/local/lib/prosody/modules" }

-- This is the list of modules Prosody will load on startup.
-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
-- Documentation for bundled modules can be found at: https://prosody.im/doc/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
}

-- These modules are auto-loaded, but should you want
-- to disable them then uncomment them here:
modules_disabled = {
        -- "offline"; -- Store offline messages
        -- "c2s"; -- Handle client connections
        -- "s2s"; -- Handle server-to-server connections
}

-- Disable account creation by default, for security
-- For more information see https://prosody.im/doc/creating_accounts
allow_registration = false

-- Debian:
--   Do not send the server to background, either systemd or start-stop-daemon take care of that.
--
daemonize = false;

-- Debian:
--   Please, don't change this option since /run/prosody/
--   is one of the few directories Prosody is allowed to write to
--
pidfile = "/run/prosody/prosody.pid";

-- Force clients to use encrypted connections? This option will
-- prevent clients from authenticating unless they are using encryption.

c2s_require_encryption = true

-- Force servers to use encrypted connections? This option will
-- prevent servers from authenticating unless they are using encryption.

s2s_require_encryption = true

-- Force certificate authentication for server-to-server connections?

s2s_secure_auth = false

-- Some servers have invalid or self-signed certificates. You can list
-- remote domains here that will not be required to authenticate using
-- certificates. They will be authenticated using DNS instead, even
-- when s2s_secure_auth is enabled.

--s2s_insecure_domains = { "insecure.example" }

-- Even if you disable s2s_secure_auth, you can still require valid
-- certificates for some domains by specifying a list here.

--s2s_secure_domains = { "jabber.org" }

-- Select the authentication backend to use. The 'internal' providers
-- use Prosody's configured data storage to store the authentication data.

authentication = "internal_hashed"

-- Select the storage backend to use. By default Prosody uses flat files
-- in its configured data directory, but it also supports more backends
-- through modules. An "sql" backend is included by default, but requires
-- additional dependencies. See https://prosody.im/doc/storage for more info.

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

-- For the "sql" backend, you can uncomment *one* of the below to configure:
--sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }


-- Archiving configuration
-- If mod_mam is enabled, Prosody will store a copy of every message. This
-- is used to synchronize conversations between multiple clients, even if
-- they are offline. This setting controls how long Prosody will keep
-- messages in the archive before removing them.

archive_expires_after = "1w" -- Remove archived messages after 1 week

-- You can also configure messages to be stored in-memory only. For more
-- archiving options, see https://prosody.im/doc/modules/mod_mam

-- Logging configuration
-- For advanced logging see https://prosody.im/doc/logging
--
-- Debian:
--  Logs info and higher to /var/log
--  Logs errors to syslog also
log = {
        -- Log files (change 'info' to 'debug' for debug logs):
        debug = "/var/log/prosody/prosody.log";
        error = "/var/log/prosody/prosody.err";
        -- Syslog:
        { levels = { "error" }; to = "syslog";  };
}

-- Uncomment to enable statistics
-- For more info see https://prosody.im/doc/statistics
-- statistics = "internal"

-- Certificates
-- Every virtual host and component needs a certificate so that clients and
-- servers can securely verify its identity. Prosody will automatically load
-- certificates/keys from the directory specified here.
-- For more information, including how to use 'prosodyctl' to auto-import certificates
-- (from e.g. Let's Encrypt) see https://prosody.im/doc/certificates

-- Location of directory to find certificates in (relative to main config file):
certificates = "certs"

-- HTTPS currently only supports a single certificate, specify it here:
--https_certificate = "/etc/prosody/certs/localhost.crt"

----------- Virtual hosts -----------
-- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
-- Settings under each VirtualHost entry apply *only* to that host.
-- It's customary to maintain VirtualHost entries in separate config files
-- under /etc/prosody/conf.d/ directory. Examples of such config files can
-- be found in /etc/prosody/conf.avail/ directory.

------ Additional config files ------
-- For organizational purposes you may prefer to add VirtualHost and
-- Component definitions in their own config files. This line includes
-- all config files in /etc/prosody/conf.d/

VirtualHost "localhost"

--VirtualHost "example.com"
--      certificate = "/path/to/example.crt"

------ Components ------
-- You can specify components to add hosts that provide special services,
-- like multi-user conferences, and transports.
-- For more information on components, see https://prosody.im/doc/components

---Set up a MUC (multi-user chat) room server on conference.example.com:
--Component "conference.example.com" "muc"
--- Store MUC messages in an archive and allow users to access it
--modules_enabled = { "muc_mam" }

---Set up an external component (default component port is 5347)
--
-- External components allow adding various services, such as gateways/
-- transports to other networks like ICQ, MSN and Yahoo. For more info
-- see: https://prosody.im/doc/components#adding_an_external_component
--
--Component "gateway.example.com"
--      component_secret = "password"
Include "conf.d/*.cfg.lua"

also the jicofo config

    jicofo {
        authentication: {
         enabled: true
         type: XMPP
         login-url: conference.racke.org
      }
     xmpp: {
        client: {
         client-proxy: focus.conference.racke.org
      }
     trusted-domains: [ "recorder.conference.racke.org" ]
      }
     bridge: {
        brewery-jid: "JvbBrewery@internal.auth.conference.racke.org"
      }
     jibri: {
        brewery-jid: "JibriBrewery@internal.auth.conference.racke.org"
        pending-timeout: 90 seconds
      }
     }

No, I meant your site’s config file. You can find it at /etc/prosody/conf.avail/your.domain.com.cfg.lua

Your jicofo.conf looks good, so we can rule that out.

plugin_paths = { "/usr/share/jitsi-meet/prosody-plugins/" }

-- domain mapper options, must at least have domain base set to use the mapper
muc_mapper_domain_base = "conference.racke.org";

external_service_secret = "94Dr7q2GPsbotl2Q";
external_services = {
     { type = "stun", host = "conference.racke.org", port = 3478 },
     { type = "turn", host = "conference.racke.org", port = 3478, transport = "udp", secret = true, ttl = 86400, algorithm = "turn" },
     { type = "turns", host = "conference.racke.org", port = 5349, transport = "tcp", secret = true, ttl = 86400, algorithm = "turn" }
};

cross_domain_bosh = false;
consider_bosh_secure = true;
-- https_ports = { }; -- Remove this line to prevent listening on port 5284

-- https://ssl-config.mozilla.org/#server=haproxy&version=2.1&config=intermediate&openssl=1.1.0g&guideline=5.4
ssl = {
    protocol = "tlsv1_2+";
    ciphers = "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384"
}

unlimited_jids = {
    "focus@auth.conference.racke.org",
    "jvb@auth.conference.racke.org"
}

VirtualHost "conference.racke.org"
    -- enabled = false -- Remove this line to enable this host
    -- authentication = "anonymous"
    authentication = "internal_hashed"
    -- Properties below are modified by jitsi-meet-tokens package config
    -- and authentication above is switched to "token"
    -- app_id="example_app_id"
    -- app_secret="example_app_secret"
    -- Assign this host a certificate for TLS, otherwise it would use the one
    -- set in the global section (if any).
    -- Note that old-style SSL on port 5223 only supports one certificate, and will always
    -- use the global one.
    ssl = {
        key = "/etc/prosody/certs/conference.racke.org.key";
        certificate = "/etc/prosody/certs/conference.racke.org.crt";
    }
    av_moderation_component = "avmoderation.conference.racke.org"
    speakerstats_component = "speakerstats.conference.racke.org"
    conference_duration_component = "conferenceduration.conference.racke.org"
    -- we need bosh
    modules_enabled = {
        "bosh";
        "pubsub";
        "ping"; -- Enable mod_ping
        "speakerstats";
        "external_services";
        "conference_duration";
        "muc_lobby_rooms";
        "muc_breakout_rooms";
        "av_moderation";
    }
    c2s_require_encryption = false
    lobby_muc = "lobby.conference.racke.org"
    breakout_rooms_muc = "breakout.conference.racke.org"
    main_muc = "conference.conference.racke.org"
    -- muc_lobby_whitelist = { "recorder.conference.racke.org" } -- Here we can whitelist jibri to enter lobby enabled rooms



    VirtualHost "guest.racke.org"
        authentication = "anonymous"
        c2s_require_encryption = false
        modules_enabled = {
            "bosh";
            "pubsub";
            "turncredentials";
            "muc_lobby_rooms";
        }
    main_muc = "conference.conference.racke.org"


Component "conference.conference.racke.org" "muc"
    restrict_room_creation = true
    storage = "memory"
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        "polls";
        --"token_verification";
        "muc_rate_limit";
    }
    admins = { "focus@auth.conference.racke.org" }
    muc_room_locking = false
    muc_room_default_public_jids = true

Component "breakout.conference.racke.org" "muc"
    restrict_room_creation = true
    storage = "memory"
    modules_enabled = {
        "muc_meeting_id";
        "muc_domain_mapper";
        --"token_verification";
        "muc_rate_limit";
    }
    admins = { "focus@auth.conference.racke.org" }
    muc_room_locking = false
    muc_room_default_public_jids = true

-- internal muc component
Component "internal.auth.conference.racke.org" "muc"
    storage = "memory"
    modules_enabled = {
        "ping";
    }
    admins = { "focus@auth.conference.racke.org", "jvb@auth.conference.racke.org" }
    muc_room_locking = false
    muc_room_default_public_jids = true

VirtualHost "auth.conference.racke.org"
    ssl = {
        key = "/etc/prosody/certs/auth.conference.racke.org.key";
        certificate = "/etc/prosody/certs/auth.conference.racke.org.crt";
    }
    modules_enabled = {
        "limits_exception";
    }
    authentication = "internal_hashed"

-- Proxy to jicofo's user JID, so that it doesn't have to register as a component.
Component "focus.conference.racke.org" "client_proxy"
    target_address = "focus@auth.conference.racke.org"

Component "speakerstats.conference.racke.org" "speakerstats_component"
    muc_component = "conference.conference.racke.org"

Component "conferenceduration.conference.racke.org" "conference_duration_component"
    muc_component = "conference.conference.racke.org"

Component "avmoderation.conference.racke.org" "av_moderation_component"
    muc_component = "conference.conference.racke.org"

Component "lobby.conference.racke.org" "muc"
    storage = "memory"
    restrict_room_creation = true
    muc_room_locking = false
    muc_room_default_public_jids = true
    modules_enabled = {
        "muc_rate_limit";
    }

 VirtualHost "guest.conference.racke.org"
    authentication = "anonymous"
    c2s_require_encryption = false
    modules_enabled = {
        "bosh";
        "pubsub";
        "turncredentials";
        "muc_lobby_rooms";
  }
    main_muc = "conference.conference.racke.org"

-- Recorder config
-- -- internal muc component, meant to enable pools of jibri and jigasi clients
Component "internal.auth.conference.racke.org" "muc"
    modules_enabled = {
        "ping";
    }
    storage = "memory"
    muc_room_cache_size = 1000

VirtualHost "recorder.conference.racke.org"
    modules_enabled = {
        "ping";
    }
    authentication = "internal_plain"

@Freddie Hi, so i digged a bit inside “all different topics” and in the end… 2 things that made it fail:

– preJoin config seems to be incompatible with recording ( disabled it in /etc/jitsi/meet/*-config.js ) → so there we get the auth issue as “recorder” - can not join the session if enabled. As the prejoin page is a nice feature and looking “pro” - is there a way of enabling it and do not loose the recording functionality again?

– than another issue: soundLoop was not installed correctly.
If found some hints in another post here:

  • login as root via ssh
  • get user jibri: su jibri
  • check the loopback: aplay -l
    → result should look like this

**** List of PLAYBACK Hardware Devices ****
card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7

Ah, yeah I’ve seen a couple of people making mention of issues with enabling the prejoin screen and recording. Try setting the prejoin screen like this in your config.js:

prejoinPageEnabled: true,

Per soundLoop, did you not do this initial part during your installation?

echo "snd-aloop" >> /etc/modules
modprobe snd-aloop
lsmod | grep snd_aloop

I just looked through your prosody config and like I suspected, there’s some misconfiguration. You have the guest VirtualHost defined twice. This is wrong. You need to remove one of them.

Thanks for having an additional look into.
Will check the proposals and give some Feedback…

As the right guest was “under” the wrong “guest” virtual host - it worked as it should even with the two definitions.

There was an issue here regarding the incompatibility between recording and the prejoin page:

The issue is supposed to be fixed, but I can’t record with the prejoin page enabled at this moment. Maybe the fact that the prejoin stuff has changed syntax could have something to do?

I ask because previously it was like this:

prejoinPageEnabled: true,

and now it’s like this:

prejoinConfig: {
    enabled: true
},