search

switnet-ltd / quick-jibri-installer

Bash installer for Jitsi Meet along with Jibri on *buntu LTS based systems | Documentation Available at the Wiki
GNU General Public License v3.0
104 stars 63 forks source link

Lobby feature isn't working #18

Closed timowevel1 closed 3 years ago

timowevel1 commented 3 years ago

Made a few installations on 5 different servers, on all the lobby feature is not working. You can activate the Lobby, but you dont see people trying to join

Prosody says: Nov 13 09:25:50 portmanager error Failed to open server port 5347 on ::1, Cannot assign requested address Nov 13 09:25:50 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281 Nov 13 09:25:50 portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281

I found out that that can be ignored.

Log says Nov 13 09:25:50 imeet.tech:muc_lobby_rooms info Lobby component loaded

What is the reason? Please check it because the problem is in the installation, it doesnt work on many different systems

Ark74 commented 3 years ago

What are your firewall rules?

Ark74 commented 3 years ago

I've tried on one instance installed just yesterday. And it's working fine, my guess is that your firewall is blocking a prosody port.

Temporary disable your current firewall rules, and try again.

Please check our wiki here for more firewall info, https://github.com/switnet-ltd/quick-jibri-installer/wiki/Firewall

If something is missing we can add that up.

timowevel1 commented 3 years ago

Mh, don't got a firewalll enabled (ufw status inactive). Enabled it for testing and added all ports, same result. The user can request to join but it doesn't show up to accept.

Ark74 commented 3 years ago

Are you using secure rooms?

timowevel1 commented 3 years ago

No, I dont. I didnt install any extras

Ark74 commented 3 years ago

Ohh, that makes sense. No auth method is almost never used, still deciding if dropping it since I'll like to introduce JWT in the future at some point. Prosody gets automagically configured by Jitsi, maintaining 3 auth methods will be annoying.

timowevel1 commented 3 years ago

So what you mean is that the Lobby feature isnt working becaus I dont got secure rooms enabled? Any way to enable it though without enabling auth methods? (the Jitsi instances are public instances, so we dont need auth methods but we need the lobby feature)

Ark74 commented 3 years ago

Sorry, i guess I didn't explained myself correctly.

This installer configures prosody for secure rooms w/lobby, we didn't have the case for public rooms yet.

Can't give a ETA but I'll try to review this shortly

timowevel1 commented 3 years ago

Thank you so much, this would be awesome!

Ark74 commented 3 years ago

@timololipop could you check the latest changes on the unstable branch, meaning before run the installer use 

git checkout unstable

to test the latest changes, thanks.

timowevel1 commented 3 years ago

Tried it, works now! Thank you!

timowevel1 commented 3 years ago

Hey, could you tell me what you changed so I can apply it to an existing installation?

Ark74 commented 3 years ago

In terms of ...? I've been working lately on several features, you might wanna check the commits on unstable to see what you prefer to do once they reach stable.

timowevel1 commented 3 years ago

In terms of enabling the lobby mode when you dont got those auth methods enabled like I mentioned. I have an existing installation, installed with your installer and now I want to enable the Lobby Mode without reinstalling the whole jitsi

Ark74 commented 3 years ago

I'll try to document that on the wiki on a opening, 'til then please check the script behaviour.