Closed yodaphone closed 3 years ago
Please run tools/test-jibri-env.sh
And share the output. Maybe we can see more specific info there.
Please run tools/test-jibri-env.sh
And share the output. Maybe we can see more specific info there.
########################################################################
Welcome to Jibri Environment Tester
########################################################################
by Software, IT & Networks Ltd
Checking for updates....
#1 -- Check repository --
This installation is using the "stable" repository.
#2 -- Check latest updates for jibri --
Jibri is installed, checking version:
jibri:all/stable 8.0-61-g99288dc-1 uptodate
Jibri is already up to date: ✔
#3 -- Check Google Chrome/driver software. --
Google Chrome 88.0.4324.182
ChromeDriver 88.0.4324.96
Google Chrome is already up to date: ✔
Chromedriver version seems according to Google Chrome: ✔
#4 -- Test kernel modules --
Great!
Module snd-aloop found!
#5 -- Test .asoundrc file --
Seems to be using the latest asoundrc file available!
#6 -- Old or new config --
What config version is this using?
> This jibri seems to be running the lastest configuration already.
If you think there maybe an error on checking you current jibri configuration.
Please report this to https://github.com/switnet-ltd/quick-jibri-installer/issues
###########################
Score: 6 out of 6
###########################
Jibri Test complete, thanks for testing.
Indeed, the other log didn't show anything weird either.
Oh, that's new. I think I need to add a new test to the list, wondering if that impact previous installations. Have you confirmed that solves the issue?
yes, i added it to my jibri.conf right below
jibri {
& it works
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"
"--ignore-certificate-errors"
]
}
Nice, :+1: This must be something on the new update from chrome. I've checked some installations but even when upgraded chrome/driver they don't seem affected.
I'll add it to the configuration. Thanks for sharing the result.
found the issue & the need to add chrome section in jibri.conf
Installed using the script on a VM. installation wen thro fine & site is up just fine
but i am unable to record or livestream the meeting
attaching the jibri log
the selenium driver is failing
jibri-log.txt
Any ideas as to why? Could it be that chrome is failing due to lack of certificate authentication?
this is a plain vanilla install. attaching the install log as well
qj-installer.log