This is a Debian Bullseye Jitsi-Meet installation.
I am trying (after a while) to get JiGasi working.
I changed the HTTPS Listen Port in Apache2 config from 443 to 8391 in order to see my Jitsi-Meet Start-Page at https://–FQN–:8931
To get there I updated ./meet/–FQN—config.js:
Furthermore I updated ./videobridge/jvb.conf
enabled = true
domain = “–FQN–:8391”
tls = true
(Not sure if this is necessary, but I did a grep -nirs on my Jitsi config.)
Everythins still looks good.
I open a Conference:
I log in as administrator
I select [INVITE] in the users dropup menu and copy the invitation link:
But the link isn’t working. The link is without the :8391 port.
Not sure how to do a Pull Request for this topic.
Maybe someone else could do that?
I was trying to avoid all this npm hassle I suffered last time when I installed from GIT, and after a year or so I ran into real problems having upgraded my Debian OS to the current release.
Another thing, the invite email message doesn’t contain the protocol prefix (https://) nor does it contain the custom port either in the invitation url presented. So the email is pretty much useless for people whose internet talents end at clicking on a link.
Is there a template for the invitation email?
I now did by adding “https://” there.
Result in my Invite-Email:
Join the meeting:
To join by phone instead, tap this: +49-911-…
Well I hope this doesn’t break somewhere else since this is not really a FQN with the https:// prefix.