Anyone using Jitsi behind Nginx

scottalanmiller

@JaredBusch said in Anyone using Jitsi behind Nginx:

@sadeghpm said in Anyone using Jitsi behind Nginx:

Hi guys.
Same problem. I have jitsi docker container behind nginx.
Where is /etc/jitsi/videobridge/sip-communicator.properties file to change values? in docker configuration files?
thanks

I don't use docker for things like this for that reason.

Same. Makes simple things hard. Jitsi is one of the easiest things to deploy... until Docker gets involved.

travisdh1

@sadeghpm said in Anyone using Jitsi behind Nginx:

Hi guys.
Same problem. I have jitsi docker container behind nginx.
Where is /etc/jitsi/videobridge/sip-communicator.properties file to change values? in docker configuration files?
thanks

It's inside the docker container. You need to start a bash shell within the container its self.

stacksofplates

@sadeghpm said in Anyone using Jitsi behind Nginx:

Hi guys.
Same problem. I have jitsi docker container behind nginx.
Where is /etc/jitsi/videobridge/sip-communicator.properties file to change values? in docker configuration files?
thanks

Don't edit files in the container. Make the sip-communicator.properties file on your host and mount it under /etc/jitsi/videobridge/sip-communicator.properties

sadeghpm

@stacksofplates
thanks guys.
bind /etc/jitsi/videobridge/sip-communicator.properties with local file and container config file updated, but problem exists! very strange!

stacksofplates

@sadeghpm said in Anyone using Jitsi behind Nginx:

@stacksofplates
thanks guys.
bind /etc/jitsi/videobridge/sip-communicator.properties with local file and container config file updated, but problem exists! very strange!

Are you using their docker-compose file? They give you a .env with all of the environment variables you need to set.

I hadn't looked at their repo. You should set all of those options as env vars not in the config itself.

Once you have the env vars set up just run docker-compose up -d

sadeghpm

@stacksofplates i use official docker-compose file and according to their documentation.

br0wnt0wn

@JaredBusch Did you change the nginx conf on the jitsi server? I followed your instructions on "Install Jitsi-Meet on Debian 9 minimal" including the nginx conf, but i'm getting a err_too_many_redirects error.

JaredBusch

@br0wnt0wn said in Anyone using Jitsi behind Nginx:

@JaredBusch Did you change the nginx conf on the jitsi server? I followed your instructions on "Install Jitsi-Meet on Debian 9 minimal" including the nginx conf, but i'm getting a err_too_many_redirects error.

That guide does not have Nginx on the Jitsi server.

br0wnt0wn

@JaredBusch When i install jitsi-meet via sudo apt-get -y install jitsi-meet, it automatically installs and configures nginx

JaredBusch

@br0wnt0wn said in Anyone using Jitsi behind Nginx:

@JaredBusch When i install jitsi-meet via sudo apt-get -y install jitsi-meet, it automatically installs and configures nginx

That quide is from almost 2 years ago. Maybe things have changed.

JaredBusch

I'm tired of dealing with stupid for a bit. let me spin up a new instance and try it

JaredBusch

Spinning up a new Debian 10 install to work from.

br0wnt0wn

Awesome, thanks!

br0wnt0wn

Ok i seem to have gotten it working. In the nginx config on the jitsi server, I commented everything from this line:

location^~ /.well-known/acme-challenge/ {

to this line:

ssl_certificate_key /etc/jitsi/meet/sub.domain.com.key;

which effectively removes the server block listening on port 4444, then moves all of the location blocks and config from the listen 4444 server block to the listen 80 server block.

stacksofplates

@sadeghpm said in Anyone using Jitsi behind Nginx:

@stacksofplates i use official docker-compose file and according to their documentation.

Yeah you shouldn't need to modify the properties file then. Just use the env vars in your .env file.

JaredBusch

@br0wnt0wn said in Anyone using Jitsi behind Nginx:

Ok i seem to have gotten it working.

Good, because I was pulled away.

phqzgunsfjror

@JaredBusch

Thank you for sharing the configuration how you put the Nginx in front of Jitsi.
I tried exactly the same way and for some reason it isn't working for me. The original post is a little old. Hence, let me ask you whether it still works for you. And let me know whether you added something in the configuration for a newer Jitsi version.

Actually I have the same behavior like described on reddit (502 Bad Gateway) : https://www.reddit.com/r/selfhosted/comments/fve1ib/jitsi_with_nginx_proxy/
The difference is I dont use docker but the normal installation on ubuntu (https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md).

Regarding ports I did:
myrouter (80, 443) -> VM1: nginx (with your config)
myrouter (10000 udp) -> VM2: jitsi

phqzgunsfjror

@phqzgunsfjror said in Anyone using Jitsi behind Nginx:

@JaredBusch

Thank you for sharing the configuration how you put the Nginx in front of Jitsi.
I tried exactly the same way and for some reason it isn't working for me. The original post is a little old. Hence, let me ask you whether it still works for you. And let me know whether you added something in the configuration for a newer Jitsi version.

Actually I have the same behavior like described on reddit (502 Bad Gateway) : https://www.reddit.com/r/selfhosted/comments/fve1ib/jitsi_with_nginx_proxy/
The difference is I dont use docker but the normal installation on ubuntu (https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md).

Regarding ports I did:
myrouter (80, 443) -> VM1: nginx (with your config)
myrouter (10000 udp) -> VM2: jitsi

It seems the jitsi team moved the documentation to somewhere else a couple of days ago ... including some more information about nginx reverse proxy.
https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart

If the installation is behind a proxying nginx server, remove /etc/nginx/modules-enabled/60-jitsi-meet.conf. Then go to /etc/nginx/site-available/your-conf and change it to listen on 443 instead of 4444 and restart nginx.

I did that on my jitsi vm and now it works like a charm. The nginx reverse proxy config above is still enough for the current jitsi version.

From my end there was nothing to do with the stuff about NAT (the restart of the jitsi vm was enough).

I hope it helps someone else. The nginx reverse proxy gives me the opportunity using multiple applications behind ports 80/443 at home.

Solved Anyone using Jitsi behind Nginx