BBB 500 error after restart

[Turkel]

Hi,

I think this post should  be created on setup forums, but somehow my request spending there :S therefore I am posting here sorry :(

I have successfully installed bbb and bbb-HTML5 and in first run it worked OK, but after restarting server I am getting Internal server error 500. I am getting some errors on bbb-config but I am not sure which one to consider :S

 bbb-conf --check results:

root@TurkelServer:~# bbb-conf --check

BigBlueButton Server 2.0.0-RC4 (1518)

                    Kernel version: 4.4.0-133-generic

                      Distribution: Ubuntu 16.04.5 LTS (64-bit)

                            Memory: 7892 MB

/var/www/bigbluebutton/client/conf/config.xml (bbb-client)

  Port test (tunnel): rtmp://con.aztut.ml

                              red5: con.aztut.ml

              useWebrtcIfAvailable: true

/opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH)

                         websocket: 93.184.238.19:7443

                    WebRTC enabled: true

/etc/nginx/sites-available/bigbluebutton (nginx)

                       server name: con.aztut.ml

                              port: 80, [::]:80

                              port: 443 ssl

                    bbb-client dir: /var/www/bigbluebutton

/var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web)

                      bbb-web host: con.aztut.ml

/var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp (API demos)

                               url: con.aztut.ml

/usr/share/red5/webapps/bigbluebutton/WEB-INF/red5-web.xml (red5)

                  voice conference: FreeSWITCH

/usr/local/bigbluebutton/core/scripts/bigbluebutton.yml (record and playback)

                     playback host: con.aztut.ml

                            ffmpeg: 4.0.2-1~16.04.york0.1

/usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml (Kurento)

                        kurentoUrl: ws://con.aztut.ml:8888/kurento

                         kurentoIp: 192.168.1.10

                    localIpAddress: 192.168.1.10

               recordScreenSharing: true

                     recordWebcams: true

                              Node: v8.11.4

                           mongoDB: v3.4.16

** Potential problems described below **

# IP does not match:

#                           IP from ifconfig: 192.168.1.10

#   /etc/nginx/sites-available/bigbluebutton: con.aztut.ml

# Warning: API URL IPs do not match host:

#

#                                IP from ifconfig: 192.168.1.10

#  /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: con.aztut.ml

....................

# Error: Could not connect to the configured hostname/IP address

#

#    https://con.aztut.ml/

#

# If your BigBlueButton server is behind a firewall, see FAQ.

nc: getaddrinfo: Temporary failure in name resolution

# Error: Unable to connect to port 1935 (RTMP) on con.aztut.ml

# Warning: The setting of 93.184.238.19 for proxy_pass in

#

#    /etc/bigbluebutton/nginx/sip.nginx

#

# does not match the local IP address (192.168.1.10).

# (This is OK if you've manually changed the values)

# Warning: The API demos are installed and accessible from:

#

#    https://con.aztut.ml/demo/demo1.jsp

#

# These API demos allow anyone to access your server without authentication

# to create/manage meetings and recordings. They are for testing purposes only.

# If you are running a production system, remove them by running:

#

#    sudo apt-get purge bbb-demo

# Error: Unable to reach default URL for presentation:

#

#    https://con.aztut.ml/default.pdf

#

# Check value for beans.presentationService.defaultUploadedPresentation in

#   /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties

root@TurkelServer:~# 

[Chad Pilkey]

The problematic errors are:

# Error: Could not connect to the configured hostname/IP address

#

#    https://con.aztut.ml/

#

# If your BigBlueButton server is behind a firewall, see FAQ.

nc: getaddrinfo: Temporary failure in name resolution

# Error: Unable to connect to port 1935 (RTMP) on con.aztut.ml

 

# Error: Unable to reach default URL for presentation:

#

#    https://con.aztut.ml/default.pdf

#

# Check value for beans.presentationService.defaultUploadedPresentation in

#   /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties

 

The errors suggest that your server is failing to resolve its domain name. The domain name resolves fine for me so the problem is likely with the DNS that you're using on your network. If you run "wget https://con.aztut.ml/bigbluebutton/api -O -" on your server it will hopefully show you what the specific problem is. If the domain name isn't resolving you can add and entry to the hosts file for manual name resolution and then try the wget again. If the name resolution is working as expected then you might be in a situation where the server can't contact itself on its public IP. In that scenario you can set the hosts file to resolve the domain to the local IP and see if that clears it up.

[Turkel]

Great! editing hosts file solved my problem.

There are till some errors still exists, I am not sure should I solve them:

** Potential problems described below **

# IP does not match:

#                           IP from ifconfig: 192.168.1.10

#   /etc/nginx/sites-available/bigbluebutton: con.aztut.ml

# Warning: API URL IPs do not match host:

#

#                                IP from ifconfig: 192.168.1.10

#  /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: con.aztut.ml

# Warning: The setting of 93.184.238.19 for proxy_pass in

#

#    /etc/bigbluebutton/nginx/sip.nginx

#

# does not match the local IP address (192.168.1.10).

# (This is OK if you've manually changed the values)

When I click log out from session I am getting redirected into this page which also tells about lowlevel error.

[Chad Pilkey]

Those messages are just warnings not errors. Those messages in particular were put in because a server installed on a network with a DHCP server might get a different IP than the one it started with. In your case though you've just set a domain name instead of the local IP address.

Can you take a screenshot of the page on logout. My guess is that the page is from whatever front-end you're using, but I don't know which one that would be.

[Turkel]

It redirects to /b and outbut is below and attaches.

"An unhandled lowlevel error occurred. The application logs may have details."

[Fred Dixon]

Hi Turkel,

Can you stop and start Greenlight and let us know if that gets you further.  

  http://docs.bigbluebutton.org/install/greenlight-v2.html#applying-env-changes

There are no env changes but the above steps will restart Greenlight.

Regards,... Fred

On Thu, Aug 23, 2018 at 5:21 PM Turkel <alizade...@gmail.com> wrote:

It redirects to /b and outbut is below and attaches.

"An unhandled lowlevel error occurred. The application logs may have details."

--
You received this message because you are subscribed to the Google Groups "bigbluebutton-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-u...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-users.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/

@bigbluebutton

[Turkel]

It shows nginx 404 page after restart, is it should be greenlight welcome page ?

[Fred Dixon]

Hi Turkel,

> I think this post should  be created on setup forums, but somehow my request spending there :S therefore I am posting here sorry :(

We approved your application to the bigbluebutton-setup mailing list, so feel free to post a follow-up to our question below.

Let's check if GreenLight is running.  Do a 

  sudo docker ps

do you see the greenlight:v2 container running?

~# docker ps

CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS              PORTS                  NAMES

4ff1651affba        bigbluebutton/greenlight:v2       "bin/start"              2 weeks ago         Up 2 weeks          0.0.0.0:6000->80/tcp   greenlight-v2

Regards,... Fred

  

On Fri, Aug 24, 2018 at 4:55 AM Turkel <alizade...@gmail.com> wrote:

It shows nginx 404 page after restart, is it should be greenlight welcome page ?

--

You received this message because you are subscribed to the Google Groups "bigbluebutton-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-u...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-users.
For more options, visit https://groups.google.com/d/optout.

[Turkel]

We approved your application to the bigbluebutton-setup mailing list, so feel free to post a follow-up to our question below.

Thanks

On my first "sudo docker ps"command it showed nothing running then I manually started "docker start greenlight-v2" and it shows below results:

root@TurkelServer:~# sudo docker ps

CONTAINER ID        IMAGE                         COMMAND             CREATED             STATUS              PORTS                  NAMES

2b79cb8ec066        bigbluebutton/greenlight:v2   "bin/start"         3 days ago          Up 5 seconds        0.0.0.0:5000->80/tcp   greenlight-v2

"https://con.aztut.ml/b" still shows same error "An unhandled lowlevel error occurred. The application logs may have details."

So restart not helped.

[Turkel]

I have made some changes in my server like added php ad some scripts to run as web app and bbb stoped working again. BBB seems very sensitive :S

I got same IP error as before and when I run"wget https://con.aztut.ml/bigbluebutton/api -O -" I am getting:

ERROR: certificate common name ‘NewMedia-NET GmbH’ doesn't match requested host name ‘con.aztut.ml’.

To connect to con.aztut.ml insecurely, use `--no-check-certificate'.

Seems like something wrong with SSL certificates. Can I reinstall bbb with bbb-install.sh script for to regenerate certificates? if this is solution :S

[Chad Pilkey]

I'm not sure where "NewMedia-NET GmbH" would have come from in the certificate information. You should only see references to "Let's Encrypt" and your own domain name. When I go to your site now and look at the certificate information I can't find any references to "NewMedia-NET GmbH".

As for the new webapp you've added, make sure you aren't trying to bind to any of the ports that BBB uses (plus local ports). Use something like 8083 for your app and then create an nginx redirect to your application.

[Turkel]

yes sorry that was temporary issue and soled, but main issue still persists which is:

[Chad Pilkey]

The problem might be that you're not starting the container the proper way. The Greenlight documentation page (http://docs.bigbluebutton.org/install/greenlight-v2.html#5-start-greenlight-20) shows two different methods for starting the container and neither involve "docker start".