![]() ![]() 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. If there are any open questions just ask me on Twitter or check the references.Jitsi is a video conferencing system that you can install on a private host. The following table shows all ports, their protocol and service. Security_groups.tf: In this file the network access ingress and egress for the instance is defined. Next I will try to explain what every configuration file is responsible for. One thing to be aware of is the rate limit on certificates from Let’s encrypt (50 certificates per week for one domain). ![]() When the setup is finished, there should be a success message from the Let’s encrypt init script. You can now connect to your instance with SSH and check the /debug.txt file. The setup can take some time depending on your EC2 instance type. Execute terraform apply to apply the changes to AWS.Execute terraform init to initialize the project and download all providers.Fill in your data in the variables.tf file.AvasDream/terraform_aws_jitsi_meetĬopy the template variables.tf file to the root of the repository.ĭescription = "Region where the instance should be located"ĭescription = "Elastic IP associated with the instance"ĭescription = "Email to use for the certificate generation"ĭescription = "Domain of the Jitsi Server" For more details see the EC2 pricing page. If the IP is allocated and not connected to an instance, you have to pay 0.005 USD per hour. When the IP is associated with a running instance, you do not pay for it. Please note the price model for elastic IPs. Here you can verify that the entry is correct. Be aware that the propagation of DNS entries can take up to 48 Hours. Change your DNS settings so that your domain name is pointing to your Elastic IP.When you start a EC2 instance you get a dynamic IPv4 address, but since we need a domain for the SSL/TLS encryption, a static IPv4 is required. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |