Github.com/jitsi/docker-jitsi-meet is correct for CentOs 7?

Hello I have VPS RAM 4 CPU good and CentOs 7 100% fresh.

I follow this steaps:

Then I run/install as ROOT:

	timedatectl set-timezone America/Bogota;date

when CentOs (as in this case) is 100% “clean” no’t include git, java, nano, perl, wget, etc…
then I run:

	yum -y update
	yum -y install git java nano perl wget
	yum install -y yum-utils device-mapper-persistent-data lvm2
	yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
	yum -y install docker
	curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
	chmod +x /usr/local/bin/docker-compose

then when I check version docker-compose version:

	[root@cia ~]# docker-compose version
	docker-compose version 1.24.1, build 4667896b
	docker-py version: 3.7.3
	CPython version: 3.6.8
	OpenSSL version: OpenSSL 1.1.0j  20 Nov 2018
	[root@cia ~]#

I need FIREWALL to avoid hackers:

	cd /usr/local/src/;rm -fv csf;wget https://download.configserver.com/csf.tgz;tar -xzf csf.tgz;cd csf;sh install.sh;
	perl /etc/csf/csftest.pl;nano /etc/csf/csf.conf; ## I put the var "TESTING" to ZERO
	csf -r;

becouse this URL (https://www2.techtalkhawke.com/news/install-jitsi-videobridge-on-centos-7) say, then I do it:

	wget https://copr-be.cloud.fedoraproject.org/results/fedpop/speex/epel-7-x86_64/00146973-speex/speex-1.2-0.23.rc2.el7.centos.x86_64.rpm
	rpm -i speex-1.2-0.23.rc2.el7.centos.x86_64.rpm
	wget https://copr-be.cloud.fedoraproject.org/results/fedpop/speexdsp/epel-7-x86_64/00146970-speexdsp/speexdsp-1.2-0.7.rc3.el7.centos.x86_64.rpm
	rpm -i speexdsp-1.2-0.7.rc3.el7.centos.x86_64.rpm

yes, I no ADD GPG key (is bad?), and I continue:

	[root@cia ~]# git --version
	git version 1.8.3.1
	[root@cia ~]#

I continue from my ignorance:

	mkdir /000;cd /000
	git clone https://github.com/jitsi/docker-jitsi-meet && cd docker-jitsi-meet
	cd /000/docker-jitsi-meet
	cp env.example .env

then in {.env} I config ONLY THIS SIX LINES:

	# Exposed HTTP port
	HTTP_PORT=80
	
	# Exposed HTTPS port
	HTTPS_PORT=443
	
	# Public URL for the web service
	PUBLIC_URL=https://subdmain-created-in-panel-domain-registrar.mysld.com
	
	# Enable Let's Encrypt certificate generation
	ENABLE_LETSENCRYPT=1
	
	# Domain for which to generate the certificate
	LETSENCRYPT_DOMAIN=subdmain-created-in-panel-domain-registrar.mysld.com
	
	# E-Mail for receiving important account notifications (mandatory)
	LETSENCRYPT_EMAIL=admin@gmail.com

and I continue with:

	./gen-passwords.sh
	mkdir -p ~/.jitsi-meet-cfg/{web/letsencrypt,transcripts,prosody,jicofo,jvb,jigasi,jibri}
	systemctl status docker

here EVER I get this answer:

	[root@cia docker-jitsi-meet]# systemctl status docker
	â docker.service - Docker Application Container Engine
	   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
	   Active: inactive (dead)
	     Docs: http://docs.docker.com
	[root@cia docker-jitsi-meet]#

then I run:

	[root@cia docker-jitsi-meet]# systemctl daemon-reload;systemctl start docker;systemctl status docker
	â docker.service - Docker Application Container Engine
	   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
	   Active: active (running) since Thu 2020-04-16 07:51:29 -05; 8ms ago
	     Docs: http://docs.docker.com
	 Main PID: 42820 (dockerd-current)
	   CGroup: /system.slice/docker.service
	           ââ42820 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --exec-opt native.cgroupd...
	           ââ42826 /usr/bin/docker-containerd-current -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-...
	
	Apr 16 07:51:28 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:28.951511288-05:00" level=warning msg="Docker could not enable SELinu... system"
	Apr 16 07:51:28 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:28.979450237-05:00" level=info msg="Graph migration to content-addres...seconds"
	Apr 16 07:51:28 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:28.980959570-05:00" level=info msg="Loading containers: start."
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.039980457-05:00" level=info msg="Firewalld running: false"
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.127540414-05:00" level=info msg="Default bridge (docker0) is assig...address"
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.174364801-05:00" level=info msg="Loading containers: done."
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.238773160-05:00" level=info msg="Daemon has completed initialization"
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.238812984-05:00" level=info msg="Docker daemon" commit="cccb291/1....n=1.13.1
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com systemd[1]: Started Docker Application Container Engine.
	Apr 16 07:51:29 subdmain-created-in-panel-domain-registrar.mysld.com dockerd-current[42820]: time="2020-04-16T07:51:29.254415135-05:00" level=info msg="API listen on /var/run/docker.sock"
	Hint: Some lines were ellipsized, use -l to show in full.
	[root@cia docker-jitsi-meet]#

becuse I see “Active: active (running)” I run:

	docker-compose up -d

and PUTTY show:

	Digest: sha256:a111a620c795ed44e9f07f0dd5c968c8ce8646cbc0ade687ded6af17c5b46a5b
	Status: Downloaded newer image for docker.io/jitsi/jvb:latest
	Creating docker-jitsi-meet_web_1     ... done
	Creating docker-jitsi-meet_prosody_1 ... done
	Creating docker-jitsi-meet_jvb_1     ... done
	Creating docker-jitsi-meet_jicofo_1  ... done
	[root@cia docker-jitsi-meet]#

finally I install this tools:

	yum -y install lsof net-tools nmap

and I get:

	[root@cia docker-jitsi-meet]# netstat -an | grep 80 | grep -i listen
	tcp6       0      0 :::80                   :::*                    LISTEN
	unix  2      [ ACC ]     STREAM     LISTENING     61070    /run/docker/libnetwork/5ad133332b6c16e13ce8069e443c0ed43e0f942570784aaf5fdfa5c32eb9dab1.sock
	[root@manizales cia docker-jitsi-meet]# netstat -an | grep 443 | grep -i listen
	tcp6       0      0 :::443                  :::*                    LISTEN
	tcp6       0      0 :::4443                 :::*                    LISTEN
	unix  2      [ ACC ]     STREAM     LISTENING     61070    /run/docker/libnetwork/5ad133332b6c16e13ce8069e443c0ed43e0f942570784aaf5fdfa5c32eb9dab1.sock
	[root@cia docker-jitsi-meet]# netstat -an | grep 10000 | grep -i listen

then from {Chrome, Firefox, Opera} I go to “subdmain-created-in-panel-domain-registrar.mysld.com” and…

NEVER, NEVER, NEVER OPEN :’(

I seek in GOOGLE then I run:

	docker ps

	[root@cia docker-jitsi-meet]# docker ps
	CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS                                              NAMES
	f703cd6426ef        jitsi/jvb           "/init"             2 minutes ago       Up 2 minutes        0.0.0.0:4443->4443/tcp, 0.0.0.0:10000->10000/udp   docker-jitsi-meet_jvb_1
	71386d9586c1        jitsi/jicofo        "/init"             2 minutes ago       Up 2 minutes                                                           docker-jitsi-meet_jicofo_1
	77860cb6e89b        jitsi/prosody       "/init"             2 minutes ago       Up 2 minutes        5222/tcp, 5269/tcp, 5280/tcp, 5347/tcp             docker-jitsi-meet_prosody_1
	7bb028362a65        jitsi/web           "/init"             2 minutes ago       Up 21 seconds       0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp           docker-jitsi-meet_web_1
	[root@cia docker-jitsi-meet]#

after I run

	docker-compose logs -f web;

and PUTTY show:

	[root@cia docker-jitsi-meet]# docker-compose logs -f web;
	Attaching to docker-jitsi-meet_web_1
	web_1      | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
	web_1      | [s6-init] ensuring user provided files have correct perms...exited 0.
	web_1      | [fix-attrs.d] applying ownership & permissions fixes...
	web_1      | [fix-attrs.d] done.
	web_1      | [cont-init.d] executing container initialization scripts...
	web_1      | [cont-init.d] 01-set-timezone: executing...
	web_1      | [cont-init.d] 01-set-timezone: exited 0.
	web_1      | [cont-init.d] 10-config: executing...
	web_1      | Saving debug log to /var/log/letsencrypt/letsencrypt.log
	web_1      | Plugins selected: Authenticator standalone, Installer None
	web_1      | Obtaining a new certificate
	web_1      | Performing the following challenges:
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Waiting for verification...
	web_1      | Challenge failed for domain manizales.vegetafood.com
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Cleaning up challenges
	web_1      | Some challenges have failed.
	web_1      | IMPORTANT NOTES:
	web_1      |  - The following errors were reported by the server:
	web_1      |    Domain: manizales.vegetafood.com
	web_1      |    Type:   dns
	web_1      |    Detail: DNS problem: SERVFAIL looking up A for
	web_1      |    manizales.vegetafood.com - the domain's nameservers may be
	web_1      |    malfunctioning
	web_1      |  - Your account credentials have been saved in your Certbot
	web_1      |    configuration directory at /etc/letsencrypt. You should make a
	web_1      |    secure backup of this folder now. This configuration directory will
	web_1      |    also contain certificates and private keys obtained by Certbot so
	web_1      |    making regular backups of this folder is ideal.
	web_1      | Failed to obtain a certificate from the Let's Encrypt CA.
	web_1      | Exiting.
	web_1      | [cont-init.d] 10-config: exited 1.
	web_1      | [cont-finish.d] executing container finish scripts...
	web_1      | [cont-finish.d] done.
	web_1      | [s6-finish] waiting for services.
	web_1      | [s6-finish] sending all processes the TERM signal.
	web_1      | [s6-finish] sending all processes the KILL signal and exiting.
	web_1      | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
	web_1      | [s6-init] ensuring user provided files have correct perms...exited 0.
	web_1      | [fix-attrs.d] applying ownership & permissions fixes...
	web_1      | [fix-attrs.d] done.
	web_1      | [cont-init.d] executing container initialization scripts...
	web_1      | [cont-init.d] 01-set-timezone: executing...
	web_1      | [cont-init.d] 01-set-timezone: exited 0.
	web_1      | [cont-init.d] 10-config: executing...
	web_1      | Saving debug log to /var/log/letsencrypt/letsencrypt.log
	web_1      | Plugins selected: Authenticator standalone, Installer None
	web_1      | Obtaining a new certificate
	web_1      | Performing the following challenges:
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Waiting for verification...
	web_1      | Challenge failed for domain manizales.vegetafood.com
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Cleaning up challenges
	web_1      | Some challenges have failed.
	web_1      | IMPORTANT NOTES:
	web_1      |  - The following errors were reported by the server:
	web_1      |    Domain: manizales.vegetafood.com
	web_1      |    Type:   dns
	web_1      |    Detail: DNS problem: SERVFAIL looking up A for
	web_1      |    manizales.vegetafood.com - the domain's nameservers may be
	web_1      |    malfunctioning
	web_1      | Failed to obtain a certificate from the Let's Encrypt CA.
	web_1      | Exiting.
	web_1      | [cont-init.d] 10-config: exited 1.
	web_1      | [cont-finish.d] executing container finish scripts...
	web_1      | [cont-finish.d] done.
	web_1      | [s6-finish] waiting for services.
	web_1      | [s6-finish] sending all processes the TERM signal.
	web_1      | [s6-finish] sending all processes the KILL signal and exiting.
	web_1      | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
	web_1      | [s6-init] ensuring user provided files have correct perms...exited 0.
	web_1      | [fix-attrs.d] applying ownership & permissions fixes...
	web_1      | [fix-attrs.d] done.
	web_1      | [cont-init.d] executing container initialization scripts...
	web_1      | [cont-init.d] 01-set-timezone: executing...
	web_1      | [cont-init.d] 01-set-timezone: exited 0.
	web_1      | [cont-init.d] 10-config: executing...
	web_1      | Saving debug log to /var/log/letsencrypt/letsencrypt.log
	web_1      | Plugins selected: Authenticator standalone, Installer None
	web_1      | Obtaining a new certificate
	web_1      | Performing the following challenges:
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Waiting for verification...
	web_1      | Challenge failed for domain manizales.vegetafood.com
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Cleaning up challenges
	web_1      | Some challenges have failed.
	web_1      | IMPORTANT NOTES:
	web_1      |  - The following errors were reported by the server:
	web_1      |    Domain: manizales.vegetafood.com
	web_1      |    Type:   dns
	web_1      |    Detail: DNS problem: SERVFAIL looking up A for
	web_1      |    manizales.vegetafood.com - the domain's nameservers may be
	web_1      |    malfunctioning
	web_1      | Failed to obtain a certificate from the Let's Encrypt CA.
	web_1      | Exiting.
	web_1      | [cont-init.d] 10-config: exited 1.
	web_1      | [cont-finish.d] executing container finish scripts...
	web_1      | [cont-finish.d] done.
	web_1      | [s6-finish] waiting for services.
	web_1      | [s6-finish] sending all processes the TERM signal.
	web_1      | [s6-finish] sending all processes the KILL signal and exiting.
	web_1      | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
	web_1      | [s6-init] ensuring user provided files have correct perms...exited 0.
	web_1      | [fix-attrs.d] applying ownership & permissions fixes...
	web_1      | [fix-attrs.d] done.
	web_1      | [cont-init.d] executing container initialization scripts...
	web_1      | [cont-init.d] 01-set-timezone: executing...
	web_1      | [cont-init.d] 01-set-timezone: exited 0.
	web_1      | [cont-init.d] 10-config: executing...
	web_1      | Saving debug log to /var/log/letsencrypt/letsencrypt.log
	web_1      | Plugins selected: Authenticator standalone, Installer None
	web_1      | Obtaining a new certificate
	web_1      | Performing the following challenges:
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Waiting for verification...
	web_1      | Challenge failed for domain manizales.vegetafood.com
	web_1      | http-01 challenge for manizales.vegetafood.com
	web_1      | Cleaning up challenges
	web_1      | Some challenges have failed.
	web_1      | IMPORTANT NOTES:
	web_1      |  - The following errors were reported by the server:
	web_1      |    Domain: manizales.vegetafood.com
	web_1      |    Type:   dns
	web_1      |    Detail: DNS problem: SERVFAIL looking up A for
	web_1      |    manizales.vegetafood.com - the domain's nameservers may be
	web_1      |    malfunctioning
	web_1      | Failed to obtain a certificate from the Let's Encrypt CA.
	web_1      | Exiting.
	web_1      | [cont-init.d] 10-config: exited 1.
	web_1      | [cont-finish.d] executing container finish scripts...
	web_1      | [cont-finish.d] done.
	web_1      | [s6-finish] waiting for services.
	web_1      | [s6-finish] sending all processes the TERM signal.
	web_1      | [s6-finish] sending all processes the KILL signal and exiting.
	[root@cia docker-jitsi-meet]#

but all continue identic: nothing load

:’(