Open elearningdienst opened 3 years ago
Have a look on the nginx configuration described https://janis-streib.de/post/pitfalls-when-setting-up-a-turnserver-with-bbb/ in Pitfall 3.
I'm somewhat confused. I can't get it to work and meanwhile think it is a IPv4/IPv6 problem. The configuration is changed like the document in the post @ReimarBauer suggests and the stream on :443 is multiplexed an the TURN works well even with other apps and video/screenshare. But not with the freeswitch container. Served several hours on that issue.
No idea how to get further...
Good Morning,
I have bbb dockerized and it seems to work exept the audio connection. I always get a connection error 1004 ICE-Error.
I have already a coturn server up and running. It is used by e.g. nextcloud talk and bbb with webcams and screenshare, I see that in the coturn logs. I tried with clients inside and outside of my LAN.
The only difference to the mentioned TURN Server configuration is, that coturn does not listen on TSL/443 but on TLS/5349
TURN_SERVER=turns:turn.eldshort.de:5349?transport=tcp TURN_SECRET=mysecret
I tried as well the hastagged parameters of .env , same effect.
The coturn machine is directly connect to the internet with IPv4 and IPv6. Both external IPs are set in the .env. The BBB Server is on another machine due that the webinterface is proxied.
EXTERNAL_IPv4=185.248.151.151 EXTERNAL_IPv6=2a00:6020:15b7:7c00:501a:96ff:fea1:d58d
This is my nginx reverse proxy conf:`map $http_upgrade $connection_upgrade { default upgrade; '' close; } map $remote_addr $endpoint_addr { "~:" <[bbb_servers_global_ipv6]>; default;
}
server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name bbb.elearningdienst.de;
ssl_certificate /etc/letsencrypt/live/bbb.elearningdienst.de-0001/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/bbb.elearningdienst.de-0001/privkey.pem;
access_log /var/log/nginx/bigbluebutton.access.log; error_log /var/log/nginx/bigbluebutton.error.log;
location / { proxy_http_version 1.1; proxy_pass http://$endpoint_addr:8080; 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_set_header X-Forwarded-Proto $scheme; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_cache_bypass $http_upgrade; }
` I already have seen https://github.com/bigbluebutton/docker/issues/142 and https://github.com/bigbluebutton/docker/issues/86 but both reccommend settings doesn't help.
I think it could be problem with the choosen port, maybe within the container is port 443 expected and not 5349? I don't now much about docker and freeswitch, so I need some help to debug that problem.