-
Notifications
You must be signed in to change notification settings - Fork 33
Integration with (existing) NGINX #87
Comments
(no issue) |
This is my working nginx config, nginx used as a reverse proxy with letsencrypt:
|
hi, thanks a lot. I already send a PR with slightly bit more elaborated example. Of course lots of it can be scraped. The hidden beast is in: ...
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
... thanks and 🍻 for you |
Hello, I have bbb on a subdomain too. |
@kodaizen : can you share your [anonymised] |
I’m still only learning about most of the stuff involved here so I may be missing something basic. My currents setup for general sites is a container from the jwilder/nginx-proxy image to handle reverse proxy along with a container from the companion image jrcs/letsencrypt-nginx-proxy-companion to handle SSL. When I use the above config modifications, the bbb-docker_https_proxy_1 container cannot start as my nginx-proxy container is already listening on ports 80 and 443. From the log:
How do I get around this? |
@MartinHarran There are a few things you need to change for jwilder's proxy. In
In
In
In
For the turn server to work you need to make some more adjustments. in
and changing file paths in
|
@MartinHarran please see also PR: https://github.com/alangecker/bigbluebutton-docker/pull/88/files |
@cjhille That worked perfectly, thank you very much for such detailed instructions |
@xpbe0 - cjhille's instructions worked perfectly, what is different in that PR that I should be looking at? |
hello @MartinHarran, there are differences in handling certs and netowrking. I didn't change anything in docker-compose.yml file. Also could be important to mention that I use branch v2.3.x |
Missing instructions in Integration with NGINX.
The text was updated successfully, but these errors were encountered: