Closed hostbbb closed 11 months ago
@hostbbb Thank you for your valuable feedback,
To resolve the error, follow these steps:
docker stop <containerId>
to stop the container. Replace <containerId>
with the actual container ID from the error message.docker rm <containerId>
to remove the container from your system.docker ps -a
and checking that the specific container ID no longer appears in the list.Remember: Before ending the meeting or closing the meeting tab, ensure that you have stopped any ongoing streaming activities.
By following these steps, you should be able to resolve the error and clean up the container causing the issue.
thanks, the docker ps -a found it. looks like the container exited and could not see with just docker ps
So its working now, but notice this first test... chrome cant play audio, needs permission. will stop and try again. let me know if logs are needed to debug why
ubuntu@play:~/bigbluebutton-streaming$ git log commit d1e3fa89843fe0c406299742d154e483a1b252c3 (HEAD -> master, origin/master, origin/HEAD) Merge: 41c6e83 2c90546
so second meeting does same thing. not getting audio permission... i reinstalled this morning, and got latest.
var options = {
headless: false,
args: [
'--disable-infobars',
'--autoplay-policy=no-user-gesture-required',
'--no-sandbox',
'--shm-size=2gb',
'--disable-dev-shm-usage',
--window-size=${width},${height}
,
'--app=https://www.google.com/',
'--start-fullscreen',
],
} this fixed the autoplay for me... assume puppeteer using newer chromium... firefox has required this for some time.
@hostbbb Thanks for testing and sharing your feedback on BigBlueButton Streaming. I'm glad to hear that the autoplay issue has been resolved with these Puppeteer options. It's always helpful to identify and address such issues to ensure a smooth user experience. If you encounter any other problems or have more feedback, feel free to let us know. Happy streaming!
Great project, installed in 2.6.10 instance... worked great as expected the first time. I stop streaming everything good.
then i enter some bogus info in the server and stream key field, hit start and saw the Live Stream user for few seconds.
However despite, doing bbb-conf --restart, a server reboot, and finally an uninstall and install again a get this same message. when i attempt again from multiple greenlight rooms, and reseting stream keys.
I can see the bbb running docker contained with docker ps, not sure how to see the bbb-streaming containers?
Any idea :)