Skip to content
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

Port 5222 has to be opened on the Jitst Meet server #270

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

goappycodes
Copy link

I believe it is very important to let users know that Port 5222 has to be opened on the Jitst Meet server to allow inbound connections. Might save a few days effort for people :)

I believe it is very important to let users know that Port 5222 has to be opened on the Jitst Meet server to allow inbound connections. Might save a few days effort for people :)
@jitsi-jenkins
Copy link

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

@bbaldino
Copy link
Member

bbaldino commented Apr 1, 2021

I'm not sure this feels like it belongs in the Jibri README, does nothing else require that port to be accessible?

@kpeiruza
Copy link

kpeiruza commented May 6, 2021

@bbaldino everything connecting remotely to Prosody needs it, i.e. videobridges, jigasi or jicofo if it's not on the same machine.

@bbaldino
Copy link
Member

bbaldino commented May 6, 2021

@bbaldino everything connecting remotely to Prosody needs it, i.e. videobridges, jigasi or jicofo if it's not on the same machine.

Right, so it seems like this would be covered by another component that would be set up well before someone got to setting up Jibri.

@Freddie-m
Copy link

Freddie-m commented May 18, 2021

@bbaldino everything connecting remotely to Prosody needs it, i.e. videobridges, jigasi or jicofo if it's not on the same machine.

True, but if everything is hosted on the same server, nothing else appears to require opening that port. It appears Jibri needs that port open (at least, if behind a NAT) regardless of where it's installed - same server as JMS or separate standalone server. Not sure if this qualifies as a PR though; a note in the README would suffice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants