Skip to content
Jitsi.help
HostingServicesGuidesTroubleshootingComparePricing
Get helpDeploy in one click

Jitsi recording setup service (Jibri)

Updated By the Jitsi Help engineering team

Short answer

We set up Jibri recording on your existing Jitsi server: the snd-aloop kernel module (including the AWS kernel fix), correctly sized recorders, as many concurrent recordings as you need, and automatic upload of every finished recording to your S3 bucket or other storage. We test real recordings end to end before handover.

What you get

  • Jibri on your server or on dedicated recorder servers
  • snd-aloop kernel module, including the AWS kernel fix
  • Concurrent recordings sized to your needs
  • Automatic upload to S3 (or compatible storage) with an IAM role
  • Firewall rules between recorders and Jitsi, locked down
  • End-to-end test: record, upload, play back

Typical timeline

1 to 3 working days

Get a quote

Recording is the Jitsi feature that fails most often, because it depends on a kernel module, a headless browser, certificates and XMPP accounts all lining up. We have debugged every one of those on production servers.

What we set up

  • Kernel and audio. snd-aloop with enough devices and substreams, including the generic kernel swap AWS needs.
  • Recorders. On your Jitsi server for light use, or dedicated recorder servers for regular recording, with matching domains and credentials.
  • Storage. Finished recordings uploaded to your S3 bucket with an instance role, then removed from disk.
  • Access. Who may start recordings, and where people find them afterwards.

Already broken?

Send us the Jibri logs through the contact form. The common causes are in Jitsi recording not working.

On our platform

Recording is a one-time $39 feature per server on our one-click platform, with all of the above built in.

Frequently asked questions

Can you fix our existing Jibri instead of rebuilding it?

Yes. Most broken Jibri setups have one of four causes, and we usually find it in the logs quickly. If the design cannot meet your needs, we explain why before proposing changes.

How many recordings can run at once?

As many as you have Jibri instances, one recording each. We size recorders to your peak and can make them scale with demand.

Stuck, or would rather not do this by hand?

Deploy it in one click

A private Jitsi server in your own AWS account with SSL, your domain and optional recording, transcription and JWT. Free 15 minute trial.

Start free trial

Talk to a Jitsi engineer

Setup, fixes, branding, recording, scaling. Tell us what is happening and we reply with a plan and a quote.

Get expert help

Related

How to record Jitsi meetings with Jibri

Set up Jibri recording for self-hosted Jitsi Meet on Docker: kernel module, env settings, scaling recorders, uploading to S3, and the three failures we see most.

Jitsi recording not working: Jibri errors and fixes

Fix Jibri recording on self-hosted Jitsi: 'Timed out waiting for call page to load', missing snd-aloop on AWS, recorder mismatches and silent files.

Jitsi transcription setup service

We add live captions and saved transcripts to self-hosted Jitsi with Jigasi and Vosk (free, private) or Google Speech, with transcripts delivered to your storage.

How to run Jitsi Meet on AWS

Deploy Jitsi Meet on Amazon EC2: instance sizes and monthly costs, security group rules, Elastic IP, DNS, SSL, and the AWS kernel issue that breaks Jibri recording.