Unable Connect to the FreeSWITCH on port 8021

[lizhiz...@gmail.com]

Hi,

My BBB(2.0 beta) is behind a firewall. When I start BBB, I can see the error of connection to port 8021. I tried to do configuration according followings,

http://docs.bigbluebutton.org/install/install.html#freeswitch-fails-to-bind-to-port-8021

http://docs.bigbluebutton.org/install/install.html#configuring-bigbluebutton-behind-a-firewall

Run bbb-conf --setip to change the IP to firewall IP address: bbb-conf --setip "123.206.254.27“

After configuration as above, it become worse, both freeswitch and nginx are not running, here is information and log I dumped, please help to take a look what I can do to resolve and bring up BBB.

zhaolz@VM-63-26-ubuntu:/etc$ sudo bbb-conf --setip 123.206.254.27 Assigning 123.206.254.27 for testing for firewall in /var/www/bigbluebutton/client/conf/config.xml Assigning 123.206.254.27 for rtmp:// in /var/www/bigbluebutton/client/conf/config.xml Assigning 123.206.254.27 for servername in /etc/nginx/sites-available/bigbluebutton Assigning 123.206.254.27 for http[s]:// in /var/www/bigbluebutton/client/conf/config.xml Assigning 123.206.254.27 for publishURI in /var/www/bigbluebutton/client/conf/config.xml Assigning 123.206.254.27 for web application URL in /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties Assigning 123.206.254.27 for web application URL in /usr/share/bbb-apps-akka/conf/application.conf Assigning 123.206.254.27 for api demos in /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp Assigning 123.206.254.27 for record and playback in /usr/local/bigbluebutton/core/scripts/bigbluebutton.yml Assigning 123.206.254.27 for playback of recordings: Restarting the BigBlueButton 2.0.0-beta ... Stopping BigBlueButton Starting BigBlueButton Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. Job for freeswitch.service failed because the control process exited with error code. See "systemctl status freeswitch.service" and "journalctl -xe" for details. zhaolz@VM-63-26-ubuntu:~$ systemctl status freeswitch ● freeswitch.service - freeswitch Loaded: loaded (/lib/systemd/system/freeswitch.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Sat 2018-02-10 16:39:27 CST; 2min 24s ago Process: 1527 ExecStart=/opt/freeswitch/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON lines 1-4/4 (END) zhaolz@VM-63-26-ubuntu:~$ zhaolz@VM-63-26-ubuntu:~$ zhaolz@VM-63-26-ubuntu:~$ systemctl status nginx ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-02-10 16:39:25 CST; 2min 49s ago Process: 1164 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited lines 1-4/4 (END)

zhaolz@VM-63-26-ubuntu:~$ zhaolz@VM-63-26-ubuntu:~$ tail -f /opt/freeswitch/log/freeswitch.log 2018-02-09 16:46:27.301076 [DEBUG] switch_scheduler.c:144 Deleting task 3 limit_hash_cleanup (mod_hash) 2018-02-09 16:46:27.301076 [INFO] switch_core_sqldb.c:1678 sofia:external Stopping SQL thread. 2018-02-09 16:46:27.301076 [DEBUG] sofia.c:3471 Write lock external 2018-02-09 16:46:27.301076 [DEBUG] sofia.c:3484 Write unlock external 2018-02-09 16:46:27.401087 [NOTICE] sofia.c:3416 Waiting for worker thread 2018-02-09 16:46:27.401087 [INFO] switch_core_sqldb.c:1720 sofia:internal Destroying SQL queue. 2018-02-09 16:46:27.601079 [INFO] switch_core_sqldb.c:1678 sofia:internal Stopping SQL thread. 2018-02-09 16:46:27.601079 [DEBUG] sofia.c:3471 Write lock internal 2018-02-09 16:46:27.601079 [DEBUG] sofia.c:3484 Write unlock internal 2018-02-09 16:46:27.601079 [WARNING] sofia.c:2295 MSG Thread Ended

zhaolz@VM-63-26-ubuntu:~$ sudo journalctl -u freeswitch -- Logs begin at Sat 2018-02-10 16:39:20 CST, end at Sat 2018-02-10 16:52:16 CST. -- Feb 10 16:39:24 VM-63-26-ubuntu systemd[1]: Starting freeswitch... Feb 10 16:39:25 VM-63-26-ubuntu freeswitch[1181]: 1279 Backgrounding. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Control process exited, code=exi Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: Failed to start freeswitch. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Unit entered failed state. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Failed with result 'exit-code'. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Service hold-off time over, sche Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: Stopped freeswitch. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: Starting freeswitch... Feb 10 16:39:25 VM-63-26-ubuntu freeswitch[1437]: 1439 Backgrounding. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Control process exited, code=exi Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: Failed to start freeswitch. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Unit entered failed state. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: freeswitch.service: Failed with result 'exit-code'. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: freeswitch.service: Service hold-off time over, sche Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: Stopped freeswitch. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: Starting freeswitch... Feb 10 16:39:26 VM-63-26-ubuntu freeswitch[1493]: 1495 Backgrounding. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: freeswitch.service: Control process exited, code=exi Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: Failed to start freeswitch. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: freeswitch.service: Unit entered failed state. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: freeswitch.service: Failed with result 'exit-code'. Feb 10 16:39:26 VM-63-26-ubuntu systemd[1]: freeswitch.service: Service hold-off time over, sche lines 2-24 zhaolz@VM-63-26-ubuntu:~$ zhaolz@VM-63-26-ubuntu:~$ zhaolz@VM-63-26-ubuntu:~$ sudo journalctl -u nginx -- Logs begin at Sat 2018-02-10 16:39:20 CST, end at Sat 2018-02-10 16:53:00 CST. -- Feb 10 16:39:24 VM-63-26-ubuntu systemd[1]: Starting A high performance web server and a reverse Feb 10 16:39:25 VM-63-26-ubuntu nginx[1164]: nginx: [emerg] unknown directive "gocation" in /etc Feb 10 16:39:25 VM-63-26-ubuntu nginx[1164]: nginx: configuration file /etc/nginx/nginx.conf tes Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: nginx.service: Control process exited, code=exited s Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: Failed to start A high performance web server and a Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: nginx.service: Unit entered failed state. Feb 10 16:39:25 VM-63-26-ubuntu systemd[1]: nginx.service: Failed with result 'exit-code'. lines 1-8/8 (END)Write failed: Connection reset by peer

zhaolz@VM-63-26-ubuntu:~$ sudo bbb-conf --check BigBlueButton Server 2.0.0-beta (704) Kernel version: 4.4.0-112-generic Distribution: Ubuntu 16.04.3 LTS (64-bit) Memory: 3784 MB /var/www/bigbluebutton/client/conf/config.xml (bbb-client) Port test (tunnel): 123.206.254.27 red5: 123.206.254.27 useWebrtcIfAvailable: true /opt/freeswitch/etc/freeswitch/sip_profiles/external.xml (FreeSWITCH) websocket port: 5066 WebRTC enabled: true /etc/nginx/sites-available/bigbluebutton (nginx) server name: 123.206.254.27 port: 80, [::]:80 bbb-client dir: /var/www/bigbluebutton /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties (bbb-web) bbb-web host: 123.206.254.27 /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp (API demos) url: 123.206.254.27 /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: 123.206.254.27 ** Potential problems described below ** # IP does not match: # IP from ifconfig: 10.141.63.26 # /etc/nginx/sites-available/bigbluebutton: 123.206.254.27 # Warning: API URL IPs do not match host: # # IP from ifconfig: 10.141.63.26 # /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: 123.206.254.27 # Not running: Nginx # Error: Found text in freeswitch.log: # # Thread ended for mod_event_socket # # FreeSWITCH may not be responding to requests on port 8021 (event socket layer) # and users may have errors joining audio. # # # Error: Unable to connect to the FreeSWITCH Event Socket Layer on port 8021 # # Warning: The voice application may not have registered with the sip server. # Try running: # # sudo bbb-conf --clean # .................... # Error: Could not connect to the configured hostname/IP address # # http://123.206.254.27/ # # If your BigBlueButton server is behind a firewall, see FAQ. # Error: Could not detect FreeSWITCH listening on port 5060 # Warning: The setting of 123.206.254.27 for proxy_pass in # # /etc/bigbluebutton/nginx/sip.nginx # # does not match the local IP address (10.141.63.26). # (This is OK if you've manually changed the values) # Warning: You are running BigBlueButton on a server with less than 4G of memory. Your # performance may suffer. # Warning: The API demos are installed and accessible from: # # http://123.206.254.27/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: # # http://123.206.254.27/default.pdf # # Check value for beans.presentationService.defaultUploadedPresentation in # /var/lib/tomcat7/webapps/bigbluebutton/WEB-INF/classes/bigbluebutton.properties zhaolz@VM-63-26-ubuntu:~$

Best Regards,

LizhiZhao

[Fred Dixon]

Hi Lizhi,

Can you post the output of

   sudo netstat -antp | grep 80

Regards,... Fred

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

--

BigBlueButton Developer

http://bigbluebutton.org/

@bigbluebutton

[Chad Pilkey]

nginx didn't start because you've got a typo in one of your configuration files.

zhaolz@VM-63-26-ubuntu:~$ sudo journalctl -u nginx -- Logs begin at Sat 2018-02-10 16:39:20 CST, end at Sat 2018-02-10 16:53:00 CST. -- Feb 10 16:39:24 VM-63-26-ubuntu systemd[1]: Starting A high performance web server and a reverse Feb 10 16:39:25 VM-63-26-ubuntu nginx[1164]: nginx: [emerg] unknown directive "gocation" in /etc

It should be "location" not "gocation". It's possible that FreeSWITCH is failing because of a typo also.

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[lizhiz...@gmail.com]

Thanks a lot, Chad, it was my mistake typo for nginx configuration. After I corrected itto "location", nginx works well

But Freeswith still has the same issue on port 8021

Hi Fred,

Here is the netstat output,

zhaolz@VM-63-26-ubuntu:/etc/bigbluebutton/nginx$ sudo netstat -antp | grep 80

tcp        0      0 0.0.0.0:5080            0.0.0.0:*               LISTEN      17580/java

tcp        0      0 127.0.0.1:8005          0.0.0.0:*               LISTEN      17653/java

tcp        0      0 0.0.0.0:5070            0.0.0.0:*               LISTEN      17580/java

tcp        0      0 0.0.0.0:9999            0.0.0.0:*               LISTEN      17580/java

tcp        0      0 0.0.0.0:1935            0.0.0.0:*               LISTEN      17580/java

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      17653/java

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      17657/nginx -g d                      aem

tcp        0      0 127.0.0.1:8080          127.0.0.1:48788         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48722         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48766         TIME_WAIT   -

tcp        0      0 127.0.0.1:59102         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:8080          127.0.0.1:48760         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48762         TIME_WAIT   -

tcp        0      0 10.141.63.26:80         111.196.211.43:10062    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 10.141.63.26:80         111.196.211.43:10066    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 127.0.0.1:8080          127.0.0.1:48758         TIME_WAIT   -

tcp        0      0 127.0.0.1:58958         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:58976         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:8080          127.0.0.1:48776         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48764         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48778         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48780         TIME_WAIT   -

tcp        0      0 127.0.0.1:59104         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:59108         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:58978         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:59098         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:8080          127.0.0.1:48770         TIME_WAIT   -

tcp        0      0 10.141.63.26:80         111.196.211.43:10061    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 127.0.0.1:8080          127.0.0.1:48782         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48720         TIME_WAIT   -

tcp        0      0 127.0.0.1:58960         127.0.0.1:6379          ESTABLISHED 17580/java

tcp        0      0 127.0.0.1:8080          127.0.0.1:48768         TIME_WAIT   -

tcp        0      0 10.141.63.26:80         111.196.211.43:10065    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 10.141.63.26:80         111.196.211.43:10055    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 127.0.0.1:8080          127.0.0.1:48774         TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48772         TIME_WAIT   -

tcp        0      0 10.141.63.26:52862      123.206.254.27:80       TIME_WAIT   -

tcp        0      0 127.0.0.1:8080          127.0.0.1:48784         TIME_WAIT   -

tcp        0      0 10.141.63.26:80         111.196.211.43:10063    ESTABLISHED 17666/nginx: wor                      ker

tcp        0      0 127.0.0.1:8080          127.0.0.1:48786         TIME_WAIT   -

tcp6       0      0 :::80                   :::*                    LISTEN      17657/nginx -g d                      aem

zhaolz@VM-63-26-ubuntu:/etc/bigbluebutton/nginx$

Best Regards,

Lizhi

在 2018年2月13日星期二 UTC+8上午5:29:21，Chad Pilkey写道：

[Fred Dixon]

Hi Lizhi,

Did you make any edits yourself to the FreeSWITCH configuration files?  Can you post the output of

 

  sudo bbb-conf --status

> # Error: Found text in freeswitch.log:

> #

> #    Thread ended for mod_event_socket

Also, check the FreeSWITCH logs in

  /opt/freeswitch/log/freeswitch.log

for startup errors. 

Regards,... Fred

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[lizhiz...@gmail.com]

Hi Fred,

Thanks for your time, I double confirmed the freeswitch log and found that one configuration was incorrect and caused the freeswitch issue. Once did correction, freeswitch became active and I did not see 8021 port issue. Looks works well, and I can join the demo1.jsp 

BTW, when I restart BBB, I saw there are several potential issues I marked as red color, but when I check BBB, it does not show issue, can you please help to double confirm the red color lines may be issues?

zhaolz@VM-63-26-ubuntu:~$ sudo bbb-conf --restart

# IP does not match:

#                           IP from ifconfig: 10.141.63.26

#   /etc/nginx/sites-available/bigbluebutton: 123.206.254.27

# Warning: API URL IPs do not match host:

#

#                                IP from ifconfig: 10.141.63.26

#  /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: 123.206.254.27

Restarting BigBlueButton 2.0.0-beta ...

Stopping BigBlueButton

Starting BigBlueButton

#    sip may not have started properly

#    bigbluebutton may not have started properly

#    screenshare-slf may not have started properly

** Potential problems described below **

# IP does not match:

#                           IP from ifconfig: 10.141.63.26

#   /etc/nginx/sites-available/bigbluebutton: 123.206.254.27

# Warning: API URL IPs do not match host:

#

#                                IP from ifconfig: 10.141.63.26

#  /var/lib/tomcat7/webapps/demo/bbb_api_conf.jsp: 123.206.254.27

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

# Warning: The setting of 123.206.254.27 for proxy_pass in

#

#    /etc/bigbluebutton/nginx/sip.nginx

#

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

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

# Warning: You are running BigBlueButton on a server with less than 4G of memory.  Your

# performance may suffer.

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

#

#    http://123.206.254.27/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

zhaolz@VM-63-26-ubuntu:~$

zhaolz@VM-63-26-ubuntu:~$

# Warning: The setting of 123.206.254.27 for proxy_pass in

#

#    /etc/bigbluebutton/nginx/sip.nginx

#

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

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

# Warning: You are running BigBlueButton on a server with less than 4G of memory.  Your

# performance may suffer.

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

#

#    http://123.206.254.27/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

zhaolz@VM-63-26-ubuntu:~$ sudo bbb-conf --status

start: inactive

red5: active

tomcat7: active

nginx: active

freeswitch: active

redis-server.service: active

libreoffice: inactive

bbb-apps-akka: active

bbb-transcode-akka: active

bbb-fsesl-akka: active

zhaolz@VM-63-26-ubuntu:~$

在 2018年2月13日星期二 UTC+8下午10:03:05，Fred Dixon写道：

[Fred Dixon]

Hi,

> # Warning: You are running BigBlueButton on a server with less than 4G of memory.  Your

> # performance may suffer.

How much memory are you running on your server?  

As it looks to be less than 4G, the server might be thrashing as it's trying to startup up all the processes, which is why you are see

> #    sip may not have started properly

> #    bigbluebutton may not have started properly

> #    screenshare-slf may not have started properly

The processes are taking too long to start as bbb-conf will only scan for expected log files for a few moments before printing the above messages.

Regards,.. Fred

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[lizhiz...@gmail.com]

Yes, Fred, my server has 4G memory.

在 2018年2月16日星期五 UTC+8下午10:15:02，Fred Dixon写道：

[Fred Dixon]

Can you post the full output of

  sudo bbb-conf --check

Regards,... Fred

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.

Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.