You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
After using this setup for a while, I realized there are more open ports on my server than there should be - especially 8080 and 8888.
I don't know how this affects security, but according to the BBB Firewall Configuration Guide, they are at least open unnecessarily.
The issue is probably caused by network_mode: host disabling docker's network isolation. Maybe there's a chance to use a different network mode?
Another solution might be binding explicitly to localhost. At least for the nginx container that should be simple, I don't know about Kurento.
If this can't be fixed in docker setup, a last resort might be using a firewall on the docker host - but this requirement should be mentioned in the README then in my opinion.
The text was updated successfully, but these errors were encountered:
According to the coturn setup instrucations running BBB (and Coturn) in any other mode than host networking is going to cause perfomance issues: instrumentisto/coturn-docker-image#3
manfred-w
pushed a commit
to manfred-w/bigbluebutton-docker
that referenced
this issue
May 18, 2021
After using this setup for a while, I realized there are more open ports on my server than there should be - especially 8080 and 8888.
I don't know how this affects security, but according to the BBB Firewall Configuration Guide, they are at least open unnecessarily.
The issue is probably caused by
network_mode: host
disabling docker's network isolation. Maybe there's a chance to use a different network mode?Another solution might be binding explicitly to localhost. At least for the
nginx
container that should be simple, I don't know about Kurento.If this can't be fixed in docker setup, a last resort might be using a firewall on the docker host - but this requirement should be mentioned in the README then in my opinion.
The text was updated successfully, but these errors were encountered: