404

Как запустить сервер Jitsi в контейнерах Docker (Nginx + Let’s Encrypt)

Установим все необходимое:

sudo apt update
sudo apt-get install git
sudo apt-get install docker.io
sudo apt-get install docker-compose

скачиваем Docker контейнер:

 git clone https://github.com/jitsi/docker-jitsi-meet.git

Производим первоначальную настройку:

cd docker-jitsi-meet
mkdir -p ~/.jitsi-meet-cfg/{web/crontabs,web/letsencrypt,transcripts,prosody/config,prosody/prosody-plugins-custom,jicofo,jvb,jigasi,jibri}
cp env.example .env
./gen-passwords.sh
nano .env

Настроем Jitsi:

HTTP_PORT=9080
HTTPS_PORT=9443
TZ=UTC
PUBLIC_URL=jitsi.example.com
DOCKER_HOST_ADDRESS=127.0.0.1
#ENABLE_AUTH=1
ENABLE_GUESTS=1
#AUTH_TYPE=internal
DISABLE_HTTPS=1
#необходимо добавить
ENABLE_XMPP_WEBSOCKET=0

Теперь запустим Jitsi: docker-compose up -d

Настройка обратного прокси-сервера и SSL

Для того чтобы можно было обращаться к нашему сайту через HTTPS, установим Nginx

sudo apt-get install nginx

Создадим файл конфигурации для Jitsi.

sudo nano /etc/nginx/conf.d/jitsi.conf

с содержимым:

server {
  server_name jitsi.example.com;

  location / {
    proxy_pass_header Authorization;
    proxy_pass http://localhost:9080;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_http_version 1.1;
    proxy_set_header Connection “”;
    proxy_buffering off;
    client_max_body_size 0;
    proxy_read_timeout 36000s;
    proxy_redirect off;
  }

   location /xmpp-websocket {
     proxy_pass http://localhost:9080/xmpp-websocket;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection "upgrade";
   }

   location /colibri-ws {
     proxy_pass http://localhost:9080;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection "upgrade";
   }
}

Где jitsi.example.com адрес для работы Jitsi, а http://localhost:9080 адрес из запущенного Docker контейнера.

Даем файлу необходимые права sudo chown www-data:www-data /etc/nginx/conf.d/jitsi.conf sudo chmod 755 /etc/nginx/conf.d/jitsi.conf Если в основном файле настроек Nginx у вас не было указано сайта, то закомментируйте все строки(символ #)

sudo nano /etc/nginx/sites-available/default

Проверить настройки можно командой

sudo nginx -t

Запустите Nginx службу sudo systemctl start nginx sudo systemctl enable nginx Либо перезагрузите ее, если она была запущена ранее sudo systemctl restart nginx

Установка SSL-сертификата с помощью Let's Encrypt.

С помощью Let's Encrypt можно бесплатно установить доверенные SSL-сертификаты на любое доменное имя. Для начала, вам необходимо установить сертификат-бота. sudo apt install certbot python3-certbot-nginx

Запускаем процесс получение сертификатов sudo certbot --nginx

Пример ответов:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
cancel): admin@example.com

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(A)gree/(C)ancel: A

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: Y

Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: example.com
2: jitsi.example.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1 2
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for example.com
http-01 challenge for mattermost.example.com
Waiting for verification...
Cleaning up challenges
Deploying Certificate to VirtualHost /etc/nginx/conf.d/jitsi.conf

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Redirecting all traffic on port 80 to ssl in /etc/nginx/conf.d/example.conf
Redirecting all traffic on port 80 to ssl in /etc/nginx/conf.d/jitsi.conf

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Congratulations! You have successfully enabled https://example.com and
https://jitsi.example.com

You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=example.com
https://www.ssllabs.com/ssltest/analyze.html?d=mattermost.example.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/example.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/example.com/privkey.pem
   Your cert will expire on 2022-06-02. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot again
   with the "certonly" option. To non-interactively renew *all* of
   your certificates, run "certbot renew"
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

 - We were unable to subscribe you the EFF mailing list because your
   e-mail address appears to be invalid. You can try again later by
   visiting https://act.eff.org.

Не забудтье на этапе Select the appropriate number [1-2] then [enter] (press 'c' to cancel): указать вариант 2, для автоматической перенастройки Nginx.

После этого обновите страницу, и сайты перейдут на https

@pavelprosto