We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is it possible to configure Jibri so that it connects to a different port than 443 (ordinary https)? I haven't found a way to include a port specification in config so that Selenium uses a different port than 443 to dial into a conference (invocation org.jitsi.jibri.selenium.pageobjects.CallPage.log() Visiting url https://example.com/room#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.analytics.disabled=true&config.p2p.enabled=false&config.prejoinPageEnabled=false&config.requireDisplayName=false )
Any ProxyPass / RewriteRule approach (I'm running this behind an Apache2 instance) has been futile so far - pointers are appreciated!
The text was updated successfully, but these errors were encountered:
Not currently possible from the jibri side, unsure if there's some proxy, etc trick that would do it
Sorry, something went wrong.
No branches or pull requests
Is it possible to configure Jibri so that it connects to a different port than 443 (ordinary https)? I haven't found a way to include a port specification in config so that Selenium uses a different port than 443 to dial into a conference (invocation org.jitsi.jibri.selenium.pageobjects.CallPage.log() Visiting url https://example.com/room#config.iAmRecorder=true&config.externalConnectUrl=null&config.startWithAudioMuted=true&config.startWithVideoMuted=true&interfaceConfig.APP_NAME="Jibri"&config.analytics.disabled=true&config.p2p.enabled=false&config.prejoinPageEnabled=false&config.requireDisplayName=false )
Any ProxyPass / RewriteRule approach (I'm running this behind an Apache2 instance) has been futile so far - pointers are appreciated!
The text was updated successfully, but these errors were encountered: