You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'm expecting:
I wanted to set up a pixel streaming application in an auto scalable group, with an internet facing load balancer. With that, I hoped users would have personal access to the engine such that they can run their own 3D experience without seeing what happens to the others.
What I've done:
I built a Cloud Formation stack as I followed the instructions given in the guide. The stack worked well. With the EC2 instances allocated, I took a snapshot and initiated a custom AMI. Then, I launched EC2 g4dn.xlarge instances with this AMI. At that point, I created an auto-scalable group and I attached a load balancer to the group.
The issues:
Several issues occurred when I tested the built application :
This error raised on console : WebRTC: ICE failed, your TURN server appears to be broken, see about:webrtc for more details
and the page is stuck on “Starting connection to server, please wait”
I tested with two instances, and if one works, the other one does not. The other one is stuck on “Starting connection to server, please wait” or “Streamer disconnected”
If a new user try to connect to the load balancer, for all the other users who are running the application, the page is reloaded.
I would be thankful for any help.
The text was updated successfully, but these errors were encountered:
I am in a similar situation. Please advise. Are the security groups in the original instructions set up to be able to handle everything coming through an Elastic Load Balancer?
If I spin everything up with an Auto Scaling Group without an ELB, I can play on EACH separate ip address individually just fine and everything works as expected. But I really need to use the Auto Scaling Group to create new instances and add them to the Load Balancer's target group and then point new players at the new instances.
edit: I'm guessing the CIDR and other security rules in the json file need to be set up such that the instances only allow contact from the load balancer?
and a small note, the default instance type in the posted json file is incorrect:
"InstanceType": {
"Description": "EC2 instance type",
"Type": "String",
"Default": "g4dn.4xlarge","
It should be "g4dn.xlarge" not 4xlarge. Tripped me up twice before I noticed.
What I'm expecting:
I wanted to set up a pixel streaming application in an auto scalable group, with an internet facing load balancer. With that, I hoped users would have personal access to the engine such that they can run their own 3D experience without seeing what happens to the others.
What I've done:
I built a Cloud Formation stack as I followed the instructions given in the guide. The stack worked well. With the EC2 instances allocated, I took a snapshot and initiated a custom AMI. Then, I launched EC2 g4dn.xlarge instances with this AMI. At that point, I created an auto-scalable group and I attached a load balancer to the group.
The issues:
Several issues occurred when I tested the built application :
This error raised on console : WebRTC: ICE failed, your TURN server appears to be broken, see about:webrtc for more details
and the page is stuck on “Starting connection to server, please wait”
I tested with two instances, and if one works, the other one does not. The other one is stuck on “Starting connection to server, please wait” or “Streamer disconnected”
If a new user try to connect to the load balancer, for all the other users who are running the application, the page is reloaded.
I would be thankful for any help.
The text was updated successfully, but these errors were encountered: