Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Jibri in docker container doesn't work
See original GitHub issueThis is the same issue as jitsi/jibri#231. Chrome inside the container tries to open “https://meet.jitsi” while should be directed to “https://external.fqdn”.
Proposed in the above issue solution probably should work. Related code is https://github.com/jitsi/jibri/blob/d566436459b5c1f1772af550d5d4c3357ceb2cee/src/main/kotlin/org/jitsi/jibri/api/xmpp/XmppApi.kt#L276 but it’s not completely clear how to preserve the old behavior. In some setups it will need to use “external.fqdn” and in some setups - xmpp_domain (which proably will be the same as “external.fqdn”).
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@netaskd
What I did, I Hardcoded my external server URL in file XmppUtils.kt It worked for me.
Try it with yours too.
@saghul Please check function getCallUrlInfoFromJid inside XmppUtils.kt and return URL with one of xmppServerHost rather than xmppDomain
I know it may break multiple host thing…
Other way would be to call all urls with all hosts and start session with first successful URL.
Fixed in https://github.com/jitsi/docker-jitsi-meet/pull/1046