Myconference site does not show


#1

I installed a new server afterI had many script errors.
I deleted the VMand created a brand new one with Ubuntu 18.04 TLS.

Installed Jitsi Meet according the github instructions and went straight to the Record and Livestream guidelines.

my publicIP 197.242.158.68 does not even start the first page and no errors in the javascript.

What is causing this problem?


#2


#3

the errors started when I implemented the following steps:
Setup the two accounts jibri will use.

prosodyctl register jibri auth.yourdomain.com jibriauthpass
prosodyctl register recorder recorder.yourdomain.com jibrirecorderpass

#4

yourdomain.com is replaced by 197.242.158.68 during implementation


#5

unregistering the users in the twolines does not reverse the situation


#6

Please,I need help. Ive gone through every resource available on github and jitsi news archive. Im trying to get recordings and livestreaming to work on 18.04TLS, but it seems to interfere with the normal working of the video conference.


#7

I also have a need to livestream to other social media networks:
like Facebook, Twitter, LinkedIn, Google+.
At least Facebook would be a great simultaneous stream.To Youtube and Facebook simultaneously.


#8

Can you upload your prosody logs?


#9
Dec 27 02:54:21 general info Hello and welcome to Prosody version 0.10.0
Dec 27 02:54:21 general info Prosody is using the select backend for connection handling
Dec 27 02:54:21 portmanager info Activated service ‘s2s’ on [::]:5269, :5269
Dec 27 02:54:21 portmanager info Activated service ‘c2s’ on [::]:5222, :5222
Dec 27 02:54:21 portmanager info Activated service ‘legacy_ssl’ on no ports
Dec 27 02:54:21 mod_posix info Prosody is about to detach from the console, disabling further console output
Dec 27 02:54:21 mod_posix info Successfully daemonized to PID 5001
Dec 27 02:54:24 mod_posix warn Received SIGTERM
Dec 27 02:54:24 general info Shutting down: Received SIGTERM
Dec 27 02:54:24 general info Shutting down…
Dec 27 02:54:24 general info Shutdown status: Cleaning up
Dec 27 02:54:24 general info Shutdown complete
Dec 27 02:54:24 general info Hello and welcome to Prosody version 0.10.0
Dec 27 02:54:24 general info Prosody is using the select backend for connection handling
Dec 27 02:54:24 portmanager info Activated service ‘component’ on [127.0.0.1]:5347, [::1]:5347
Dec 27 02:54:24 portmanager info Activated service ‘s2s’ on [::]:5269, :5269
Dec 27 02:54:24 portmanager info Activated service ‘c2s’ on [::]:5222, :5222
Dec 27 02:54:24 portmanager info Activated service ‘legacy_ssl’ on no ports
Dec 27 02:54:24 mod_posix info Prosody is about to detach from the console, disabling further console output
Dec 27 02:54:24 mod_posix info Successfully daemonized to PID 7110
Dec 27 02:54:24 portmanager info Activated service ‘http’ on [::]:5280, :5280
Dec 27 02:54:24 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 02:54:24 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 02:54:24 portmanager info Activated service ‘https’ on no ports
Dec 27 02:54:25 c2s55ba621d7dc0 info Client connected
Dec 27 02:54:25 jcp55ba624cb7b0 info Incoming Jabber component connection
Dec 27 02:54:25 focus.197.242.158.68:component info External component successfully authenticated
Dec 27 02:54:26 c2s55ba621d7dc0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Dec 27 02:54:26 c2s55ba621d7dc0 info Authenticated as focus@auth.197.242.158.68
Dec 27 02:54:26 jitsi-videobridge.197.242.158.68:component warn Component not connected, bouncing error for:
Dec 27 02:54:27 jcp55ba62524090 info Incoming Jabber component connection
Dec 27 02:54:27 jitsi-videobridge.197.242.158.68:component info External component successfully authenticated
Dec 27 03:00:05 mod_bosh info New BOSH session, assigned it sid ‘f8842b11-27d8-4784-8f5e-cfb31633c8c4’
Dec 27 03:00:05 boshf8842b11-27d8-4784-8f5e-cfb31633c8c4 info Authenticated as d45216aa-bf30-416c-b977-d561e75c2582@197.242.158.68
Dec 27 03:00:53 mod_bosh info New BOSH session, assigned it sid ‘e3707f55-22e3-4152-9c4b-e955e4ea4d8b’
Dec 27 03:00:53 boshe3707f55-22e3-4152-9c4b-e955e4ea4d8b info Authenticated as 18b79ee1-4db3-4be4-909f-e7ea6ceda192@197.242.158.68
Dec 27 03:01:20 boshf8842b11-27d8-4784-8f5e-cfb31633c8c4 info BOSH client disconnected
Dec 27 03:01:44 mod_bosh info New BOSH session, assigned it sid ‘12517ab9-2a4e-4ea5-ae6c-375cfe60ac91’
Dec 27 03:01:44 bosh12517ab9-2a4e-4ea5-ae6c-375cfe60ac91 info Authenticated as 9d866694-1ff2-44a3-bfcd-acffa9d4b095@197.242.158.68
Dec 27 03:02:23 mod_bosh info New BOSH session, assigned it sid ‘691ddcff-ac93-4cac-8b6e-d15fb2d6a548’
Dec 27 03:02:24 bosh691ddcff-ac93-4cac-8b6e-d15fb2d6a548 info Authenticated as 77ca04d4-ac74-4746-8e3a-85ab707845de@197.242.158.68
Dec 27 03:03:27 mod_bosh info New BOSH session, assigned it sid ‘3c769b52-812f-435e-b53a-88eba6db1058’
Dec 27 03:03:30 bosh3c769b52-812f-435e-b53a-88eba6db1058 info Authenticated as d93243de-c3c4-4a55-ba16-054b7f7bbba6@197.242.158.68
Dec 27 03:06:26 bosh3c769b52-812f-435e-b53a-88eba6db1058 info BOSH client disconnected
Dec 27 03:06:30 bosh691ddcff-ac93-4cac-8b6e-d15fb2d6a548 info BOSH client disconnected
Dec 27 03:06:34 bosh12517ab9-2a4e-4ea5-ae6c-375cfe60ac91 info BOSH client disconnected
Dec 27 03:07:46 boshe3707f55-22e3-4152-9c4b-e955e4ea4d8b info BOSH client disconnected
Dec 27 03:12:25 mod_posix warn Received SIGTERM
Dec 27 03:12:25 general info Shutting down: Received SIGTERM
Dec 27 03:12:25 c2s55ba621d7dc0 info Client disconnected: connection closed
Dec 27 03:12:25 jcp55ba624cb7b0 info component disconnected: focus.197.242.158.68 (false)
Dec 27 03:12:25 jcp55ba62524090 info component disconnected: jitsi-videobridge.197.242.158.68 (false)
Dec 27 03:12:25 general info Shutting down…
Dec 27 03:12:25 general info Shutdown status: Cleaning up
Dec 27 03:12:25 general info Shutdown complete
Dec 27 03:12:25 general info Hello and welcome to Prosody version 0.10.0
Dec 27 03:12:25 general info Prosody is using the select backend for connection handling
Dec 27 03:12:25 portmanager info Activated service ‘s2s’ on [::]:5269, :5269
Dec 27 03:12:25 portmanager info Activated service ‘c2s’ on [::]:5222, :5222
Dec 27 03:12:25 portmanager info Activated service ‘legacy_ssl’ on no ports
Dec 27 03:12:25 mod_posix info Prosody is about to detach from the console, disabling further console output
Dec 27 03:12:25 mod_posix info Successfully daemonized to PID 14481
Dec 27 03:12:25 portmanager info Activated service ‘component’ on [127.0.0.1]:5347, [::1]:5347
Dec 27 03:12:25 portmanager info Activated service ‘http’ on [::]:5280, :5280
Dec 27 03:12:25 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 03:12:25 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 03:12:25 portmanager info Activated service ‘https’ on no ports
Dec 27 03:12:27 jcp559126e1d280 info Incoming Jabber component connection
Dec 27 03:12:27 callcontrol.197.242.158.68:component info External component successfully authenticated
Dec 27 03:12:30 jcp559126e0e260 info Incoming Jabber component connection
Dec 27 03:12:30 focus.197.242.158.68:component info External component successfully authenticated
Dec 27 03:12:31 c2s559126f37060 info Client connected
Dec 27 03:12:31 c2s559126f37060 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Dec 27 03:12:31 c2s559126f37060 info Authenticated as focus@auth.197.242.158.68
Dec 27 03:12:31 jitsi-videobridge.197.242.158.68:component warn Component not connected, bouncing error for:
Dec 27 03:12:37 jcp559126f98490 info Incoming Jabber component connection
Dec 27 03:12:37 jitsi-videobridge.197.242.158.68:component info External component successfully authenticated
Dec 27 03:13:21 mod_bosh info New BOSH session, assigned it sid ‘ddf648b9-3a93-4e6c-9115-5b3ab1b4171b’
Dec 27 03:13:21 boshddf648b9-3a93-4e6c-9115-5b3ab1b4171b info Authenticated as 1154261a-1c07-4ea0-82a5-bc72d19fcebe@197.242.158.68
Dec 27 03:14:06 c2s55912712d570 info Client connected
Dec 27 03:14:06 c2s55912712d570 info Client disconnected: ssl handshake error: sslv3 alert certificate unknown
Dec 27 03:14:31 c2s559127180650 info Client connected
Dec 27 03:14:31 c2s559127180650 info Client disconnected: ssl handshake error: sslv3 alert certificate unknown
Dec 27 03:33:00 boshddf648b9-3a93-4e6c-9115-5b3ab1b4171b info BOSH client disconnected
Dec 27 22:03:50 mod_bosh info New BOSH session, assigned it sid ‘7c77f526-db68-4b28-96dd-77a1e9992fa4’
Dec 27 22:03:50 bosh7c77f526-db68-4b28-96dd-77a1e9992fa4 info Authenticated as 37b903ae-7879-4b94-9edf-c85b691babf7@197.242.158.68
Dec 27 22:04:22 mod_bosh info New BOSH session, assigned it sid ‘e8b380db-0f82-4f8a-a3ee-04d8d98a5e3e’
Dec 27 22:04:22 boshe8b380db-0f82-4f8a-a3ee-04d8d98a5e3e info Authenticated as bcef726f-66ac-45b1-8446-6fd60da21a36@197.242.158.68
Dec 27 22:04:51 mod_bosh info New BOSH session, assigned it sid ‘c40e7340-68ce-4a1a-acb7-210d969e5571’
Dec 27 22:04:52 boshc40e7340-68ce-4a1a-acb7-210d969e5571 info Authenticated as 22992aae-7947-442b-a67f-61750ed7f1fa@197.242.158.68
Dec 27 22:05:47 boshc40e7340-68ce-4a1a-acb7-210d969e5571 info BOSH client disconnected
Dec 27 22:05:49 boshe8b380db-0f82-4f8a-a3ee-04d8d98a5e3e info BOSH client disconnected
Dec 27 22:06:24 bosh7c77f526-db68-4b28-96dd-77a1e9992fa4 info BOSH client disconnected
Dec 27 22:41:49 mod_posix warn Received SIGTERM
Dec 27 22:41:49 general info Shutting down: Received SIGTERM
Dec 27 22:41:49 c2s559126f37060 info Client disconnected: connection closed
Dec 27 22:41:49 jcp559126f98490 info component disconnected: jitsi-videobridge.197.242.158.68 (false)
Dec 27 22:41:49 jcp559126e0e260 info component disconnected: focus.197.242.158.68 (false)
Dec 27 22:41:49 jcp559126e1d280 info component disconnected: callcontrol.197.242.158.68 (false)
Dec 27 22:41:49 general info Shutting down…
Dec 27 22:41:49 general info Shutdown status: Cleaning up
Dec 27 22:41:49 general info Shutdown complete

#10
Dec 27 02:54:24 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 02:54:24 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 03:12:25 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281
Dec 27 03:12:25 portmanager error Error binding encrypted port for https: No key present in SSL/TLS configuration for https port 5281

#11

In the screenshot that you shared with us I noticed that using an IP to access Jitsi Meet. That usually leads to problems. Have you configured a hostname as well? What’s in your config.hosts?


#12

Hi George

I cant find a config.hosts file. Are your referring to config.json or maybe host.conf?

I dont want to use the Public IP as the web address. I`ve been reading up on using a web name, but I find solutions for intranet ; not public IP.

Will that solve my problem with the conference system?


#13

I was referring to the hosts section of your config.json file, I’m sorry for the confusion.

I see, you should be fine if you assign a static IP to your server (which seems to be the case here).

I personally don’t see anything wrong in the Prosody logs :frowning: The BOSH URL is fronted by nginx so the SSL/TLS errors for https can be ignored.

Could you please you increase the logging level to debug and then try again? Also please post all the errors in the JavaScript console as well as the Prosody debug logs.


#14

Then again, this doesn’t look normal. The client connects and then immediately disconnects. I wonder where this is coming from…


#15

I`ve been trying to get jibri installed. It is at the exact point where the two users are loaded, that jitsi stops working


#16
  1. I would really like to use a domain name rather than the public IP as the address for conference. It will deal with the security exception that every new browser will prompt.

We have a domain bassphone.co.za and I created a subdomain meet.bassphone.co.za. Linux requires a public IP to be visible to the public. will jitsi meet work with meet.bassphone.co.za as the public URL instead of the public IP, for public URL access?

If I change the config.json everywhere 197.242.158.68 is typed with meet.bassphone.co.za will Jitsi continue working?

I dont get javascript errors this time. This is my third time buidling jitsi from scratch, trying to solve the problem.

How do I increase the logging level.
I have posted the prosody log above.


#17

wait, I am getting errors now:


#18

What do you think? It is my third time rebuidling the server from scratch, to get Jibri to work. That is why I know it is at the point of

prosodyctl register jibri auth.yourdomain.com jibriauthpass
prosodyctl register recorder recorder.yourdomain.com jibrirecorderpass

that the conference interface stops working.

I`m installing Ubuntu 18.04 TLS;will it help if I delete everything and install from OS and up again?


#19

I just tested it and it connects successfully, but needs to use the domain name configured, not the ip address as in your screenshot. But I receive an error that jicofo is not connected and not working, you need to check jicofo logs, and see why it is not working.


#20

Hi Damian

You may close this incident and respond to Videoconference keep saying “unfortunately something went wrong”

Both incidents have the same objectives and experience the same problem. I have sent you the jicofo log on this one last night.

Let`s work with this one, that is furthest in terms of info shared: Videoconference keep saying “unfortunately something went wrong”