Disconnection after add #secure-domain

First of all, thanks for the great library.
Just addes jitsi-meet to my own server and word pretty well.
Then, when added secure-domain noted that after the host is logged in, as soon as another user try to reach the url, the connection in both browser windows is lost.

Here are some js logs

2020-03-31T15:19:35.384Z [modules/UI/videolayout/VideoLayout.js] <changeUserAvatar>:  Missed avatar update - no small video yet for local react_devtools_backend.js:6:5119
2020-03-31T15:19:35.409Z [conference.js] <_onConferenceFailed>:  CONFERENCE FAILED: conference.videobridgeNotAvailable react_devtools_backend.js:6:5119
2020-03-31T15:19:35.607Z [modules/UI/videolayout/VideoLayout.js] <removeParticipantContainer>:  No remote video for 3bcc61ec react_devtools_backend.js:6:5119
2020-03-31T15:19:35.620Z [modules/xmpp/strophe.util.js] <t.a/i.Strophe.log>:  Strophe: Disconnect was called because: undefined

Then tries to reconnect automatically but is the same loop.

On the other hand, getting the following error when sudo service prosody status:

portmanager: Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

Hope all the information provided is helpful to debug the issue. Thanks!

Check your jvb logs.

Thanks @damencho for the reply.

This is what I see doing sudo tail -f /var/log/jitsi/jvb.log

2020-04-01 06:32:32.162 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:32:42.163 INFO: [17] Videobridge.createConference#326: create_conf, id=d1d78331dce386aa gid=null logging=false
2020-04-01 06:32:42.166 INFO: [17] Health.doRun#294: Performed a successful health check in 4ms. Sticky failure: false
2020-04-01 06:32:52.167 INFO: [17] Videobridge.createConference#326: create_conf, id=6a42fe2302d96d96 gid=null logging=false
2020-04-01 06:32:52.173 INFO: [17] Health.doRun#294: Performed a successful health check in 6ms. Sticky failure: false
2020-04-01 06:32:59.160 INFO: [16] VideobridgeExpireThread.expire#144: Running expire()
2020-04-01 06:33:02.174 INFO: [17] Videobridge.createConference#326: create_conf, id=30bd061053949223 gid=null logging=false
2020-04-01 06:33:02.177 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:33:12.178 INFO: [17] Videobridge.createConference#326: create_conf, id=9b368d7237e29369 gid=null logging=false
2020-04-01 06:33:12.181 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:33:22.181 INFO: [17] Videobridge.createConference#326: create_conf, id=ed156919289ed32c gid=null logging=false
2020-04-01 06:33:22.189 INFO: [17] Health.doRun#294: Performed a successful health check in 8ms. Sticky failure: false
2020-04-01 06:33:32.190 INFO: [17] Videobridge.createConference#326: create_conf, id=a43fd65f471d5202 gid=null logging=false
2020-04-01 06:33:32.193 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:33:42.193 INFO: [17] Videobridge.createConference#326: create_conf, id=3a9db09fb624a999 gid=null logging=false
2020-04-01 06:33:42.196 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:33:52.196 INFO: [17] Videobridge.createConference#326: create_conf, id=e7309e8cba2c984 gid=null logging=false
2020-04-01 06:33:52.199 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:33:59.160 INFO: [16] VideobridgeExpireThread.expire#144: Running expire()
2020-04-01 06:34:02.199 INFO: [17] Videobridge.createConference#326: create_conf, id=59ff1aef17de5a09 gid=null logging=false
2020-04-01 06:34:02.203 INFO: [17] Health.doRun#294: Performed a successful health check in 4ms. Sticky failure: false
2020-04-01 06:34:12.203 INFO: [17] Videobridge.createConference#326: create_conf, id=4a05be412ea0e945 gid=null logging=false
2020-04-01 06:34:12.206 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:34:22.207 INFO: [17] Videobridge.createConference#326: create_conf, id=da98eac127f44695 gid=null logging=false
2020-04-01 06:34:22.210 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false
2020-04-01 06:34:32.211 INFO: [17] Videobridge.createConference#326: create_conf, id=3cdae150a2cfb036 gid=null logging=false
2020-04-01 06:34:32.215 INFO: [17] Health.doRun#294: Performed a successful health check in 4ms. Sticky failure: false
2020-04-01 06:34:42.215 INFO: [17] Videobridge.createConference#326: create_conf, id=2ec901c84ab7b72f gid=null logging=false
2020-04-01 06:34:42.222 INFO: [17] Health.doRun#294: Performed a successful health check in 7ms. Sticky failure: false
2020-04-01 06:34:52.222 INFO: [17] Videobridge.createConference#326: create_conf, id=1aaa7b2f341dfd70 gid=null logging=false
2020-04-01 06:34:52.225 INFO: [17] Health.doRun#294: Performed a successful health check in 3ms. Sticky failure: false

In case could be helpful, going backwards to remove the secure domain layer I found that:

  • changing back authentication = "internal_plain" into authentication = "anonymous" on the file /etc/prosody/conf.avail/[your-hostname].cfg.lua file, still continue asking host password so,
  • commenting the line anonymousdomain: '…', on the file /etc/jitsi/meet/[your-hostname]-config.js, doesn’t ask the password but the Unfortunately, something went wrong error continuously remains, so
  • changing back the string org.jitsi.jicofo.auth.URL=XMPP:jitsi-meet.example.com into org.jitsi.jicofo.BRIDGE_MUC=JvbBrewery@internal.auth.[your-hostname] everything works as expected again!

After each step I restarted each process like:

service jicofo restart
service jitsi-videobridge2 restart
service prosody restart

Seems that the step 3 of this tutotrial is responsible for the wrong behaviour, any idea?

Thanks in advance,

In your /etc/jitsi/jicofo/sip-communicator.properties you need to have both lines, it’s not a replace, but it’s an added line. So mine looks like this:

org.jitsi.jicofo.auth.URL=XMPP:jitsi-meet.example.com
org.jitsi.jicofo.BRIDGE_MUC=JvbBrewery@internal.auth.[your-hostname]

Before that change I kept on having issues. Also changed my /etc/jitsi/jicofo/config to include the password for the focus user under the JICOFO_AUTH_PASSWORD param

Now everything works.

1 Like

Hey @Arnold thanks for your reply. Regarding the last part you included in /etc/jitsi/jicofo/config I already have a JICOFO_AUTH_USER=focus and JICOFO_AUTH_PASSWORD already set. Did you change it in some way?

However with the suggestion you gave me, and after restart all the services, everything seems work well. Let’s try later with more connections.

Thank you!!

I had some issues with a SRAM-SSH error that disappeared after I changed the password in that file. There was a password there, but after following the complete steps in https://github.com/jitsi/jicofo I realized that I had changed the password for the focus user, so I updated the /etc/jitsi/jicofo/config with the password I generated. Then the auth error also disappeared.

1 Like