Closed hrauvc closed 4 months ago
For help & support, please refer to the forum mentioned in the README. There, you’ll find answers to similar questions I have already addressed. Make sure to set the inbound rules, including port ranges, and use the EC2 elastic IP as the announcedAddress in the config.js. For more details, visit the forum. Cheers!
MiroTalk forum
First I am going to share how I have the infrastructure
1. I have an Ec2 instance on a private subnet
2. These are the security groups associated with the instance
3. I have the load balancer pointing to my instance
And so are the listening agents
4. The target group:
And its destiny
On route 53 I point to the load balancer:
The app works
And Start the meeting
But after a moment this happens:
And if another user enters it looks like this:
No errors here:
This is my nginx file: `# HTTP — proxy all requests to the Node app server { listen 80; listen [::]:80; server_name meet.dbcloud.academy;
}`
I have not placed the ssl here since otherwise it will get into a loop with AWS