-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Few installation tips and disambiguation for AWS EC2 users #104
Comments
That would definitely be welcome. |
Hello I am trying to Install Jitsi Meet in AWS EC2 Instance to achieve the following
Can you help me ? Anand |
hey. thanks for sharing. How can I DM you? Thanks. |
have you done it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I've managed to install Jitsi-meet and Jibri on a single EC2 instance and learned something that I wish I knew a few days ago so I thought I'd be nice to share:
Installing ALSA loopback module on default kernel fails so I followed the instructions here to make
modprobe snd-aloop
possible. That is, changing and updating the kernel boot settings from Linux 4.4.0-xxxx-aws to Linux 4.4.0-xxxx-generic and restarting the instance.If you you run both jitsi-meet and jibri on a t2.micro instance, you're most likely encouter a memory overflow error like this as soon as you start streaming:
INFO: [50] ffmpeg.run() [x11grab @ 0xf4e940] Cannot get 3686432 bytes of shared memory: Cannot allocate memory.
In my case, switching the instance to a r4.large solved the issue.(not only for AWS users) Despite what the README.md says, there is no "recording button" (I tried to find a button with this exact name). The "Go live now" is the button you are looking for :)
As for user/group, I've installed and ran everything as root and it worked out perfectly.
By the way, the versions I used are
I'm more than happy to open a PR to make changes on README.md.
The text was updated successfully, but these errors were encountered: