由于nginx的配置无效,无法使用自定义ssl证书运行BigBlueButton

tyu7yeag  于 2023-11-17  发布在  Nginx
关注(0)|答案(1)|浏览(195)

我正在尝试在我的家庭服务器上安装BigBlueButton,运行在Ubuntu 20.04下,使用以下command

  1. $ sudo ./bbb-install.sh -w -v focal-270 -s bigbluebutton.mycustomdomain.org

字符串
我已经为我的域bigbluebutton.mycustomdomain.org提供了有效的Lets'Encrypt SSL证书。
不确定我是否应该发布上面命令的整个输出,但我尝试了-e-x-d(我的证书文件符号链接到/local/certs)选项(单独)和没有这些选项。每次我都得到相同的结果:

  1. # Potential problems described below
  2. curl: (60) SSL: no alternative certificate subject name matches target host name 'bigbluebutton.mycustomdomain.org'
  3. More details here: https://curl.haxx.se/docs/sslcerts.html
  4. curl failed to verify the legitimacy of the server and therefore could not
  5. establish a secure connection to it. To learn more about this situation and
  6. how to fix it, please visit the web page mentioned above.
  7. .curl: (60) SSL: no alternative certificate subject name matches target host name 'bigbluebutton.mycustomdomain.org'
  8. More details here: https://curl.haxx.se/docs/sslcerts.html


当我在浏览器中打开https://bigbluebutton.mycustomdomain.org时,我会看到nginx默认的欢迎页面(或我的其他配置了nginx的网站),其中包含一条消息,即SSL证书无效,因为它与另一个域相关。
这是由安装脚本生成的nginx配置文件/etc/nginx/sites-available/bigbluebutton(并从/etc/nginx/sites-enabled/bigbluebutton链接):

  1. server_tokens off;
  2. server {
  3. listen 80;
  4. listen [::]:80;
  5. server_name bigbluebutton.mycustomdomain.org;
  6. location ^~ / {
  7. return 301 https://$server_name$request_uri; #redirect HTTP to HTTPS
  8. }
  9. location ^~ /.well-known/acme-challenge/ {
  10. allow all;
  11. default_type "text/plain";
  12. root /var/www/bigbluebutton-default/assets;
  13. }
  14. location = /.well-known/acme-challenge/ {
  15. return 404;
  16. }
  17. }
  18. set_real_ip_from 127.0.0.1;
  19. real_ip_header proxy_protocol;
  20. real_ip_recursive on;
  21. server {
  22. # this double listenting is intended. We terminate SSL on haproxy. HTTP2 is a
  23. # binary protocol. haproxy has to decide which protocol is spoken. This is
  24. # negotiated by ALPN.
  25. #
  26. # Depending on the ALPN value traffic is redirected to either port 82 (HTTP2,
  27. # ALPN value h2) or 81 (HTTP 1.0 or HTTP 1.1, ALPN value http/1.1 or no value)
  28. listen 127.0.0.1:82 http2 proxy_protocol;
  29. listen [::1]:82 http2;
  30. listen 127.0.0.1:81 proxy_protocol;
  31. listen [::1]:81;
  32. server_name bigbluebutton.mycustomdomain.org;
  33. # nginx does not know its external port/protocol behind haproxy, so use relative redirects.
  34. absolute_redirect off;
  35. # HSTS (uncomment to enable)
  36. #add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
  37. access_log /var/log/nginx/bigbluebutton.access.log;
  38. # This variable is used instead of $scheme by bigbluebutton nginx include
  39. # files, so $scheme can be overridden in reverse-proxy configurations.
  40. set $real_scheme "https";
  41. # BigBlueButton landing page.
  42. location / {
  43. root /var/www/bigbluebutton-default/assets;
  44. try_files $uri @bbb-fe;
  45. }
  46. # Include specific rules for record and playback
  47. include /etc/bigbluebutton/nginx/*.nginx;
  48. }


我不是nginxMaven,但将我的SSL证书配置放入此文件(就像我通常为其他网站所做的那样)显然不起作用:

  1. ssl_certificate /etc/letsencrypt/live/bigbluebutton.mycustomdomain.org/fullchain.pem;
  2. ssl_certificate_key /etc/letsencrypt/live/bigblugbutton.mycustomdomain.org/privkey.pem;


我认为原因是没有server块用于https连接的443端口。我还注意到include /etc/bigbluebutton/nginx/*.nginx;在文件的末尾,但似乎与服务器主机配置无关。
因此,我的问题是:如何正确配置BigBlueButton以接受我(现有)的SSL证书?

wfsdck30

wfsdck301#

@ezze
好的,请注意这是在BBB 2.7,我发现这后,研究的源代码

  1. Certificate path:
  2. /etc/haproxy/certbundle.pem
  3. Pls combine your custom certificate to "certbundle.pem"
  4. 1.chain=intermediate+root
  5. 2.fullchain=cert+chain
  6. 3.certbundle=fullchain+privatekey

字符串

相关问题