![]() ![]() Lets Encrypt supports SAN names so you can use nginx to proxy traffic to the correct service based on server name. Best option is to use lets encrypt alt method for validation usingġ) Run all services on 1 host. And we dont have that mapped to Jitsi anymore. LetsEncrypt renews the certificated using port 80 and 443. Test it by hitting and you should get the jitsi home page and be able to start a conference. FIXME: use XEP-0156 to discover it.Īnd that’s it. Update the ‘bosh:’ value to include port 444 // BOSH URL. To get the Jitsi frontend to answer on TCP/444 we need to edit the following:Įdit /etc/nginx/sites-available/nf So for Step 3, you should have the following ports forwarded into Jitsi: TCP/80 -> original host tcp/80 Create new port forward entries for TCP/444 to the Jitsi host. Switch your router TCP/80 and TCP/443 back to the original host. If you can, then the default Jitsi is done. You should be able to connect to your Jitsi service on https port 443 at this point. This setup gets you the default jitsi install using nginx and videobridge2. The basic Jitsi setup is located here Jitsi Quick Setup. So for Step 1, you should have the following ports forwarded into Jitsi: disabled TCP/80 -> original host tcp/80ĭisabled TCP/443 -> original host tcp/443 Add the additional ports Jitsi needs TCP/4443 and UDP/10000. This is just for the quick install and is switched back after the install is completed. I changed my perimeter router to forward TCP/80 and TCP/443 away from the original host to the new Jitsi host. The easiest way to handle this is to just temporarily give the Jitsi host the 80/443 that it needs. I found that when Jitsi installs it is expecting to have the default ports 80 and 443 available. Add port forward for 444 to Jitsi host.Ĥ) Edit the configs for new port, restart and test. The basic overview on how I got this to work ran like this :ġ) Switch router 80/443 ports to point to the host that will host Jitsi.ģ) Switch router 80/443 back to original host. Since I could not find a step by step guide on how to so this, I worked it out and am posting this here for anyone who wants Jitsi to run on a custom port. Since I already run stuff on TCP/443 I needed Jitsi to run on some other port. Like most people, I get 1 public IP from my ISP. I chose to run my own server so that decrypted communication is kept on a server I control running in my garage. Traffic is encrypted from client to server, but is decrypted at the server in order to relay the audio/video to conference participants. Jitsi is a video conferencing system that you can install on a private host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |