Please Advise : Over the Internet Pixel Streaming (4.24)

Community Community & Industry Discussion
1

Good Afternoon,

I am having trouble setting up pixel streaming outside of my own network. I have it working internally but not so much luck externally. I am using the Turn server and I followed go knows how many tutorial to the letter and still no go. I opened every port and turned off antivirus software and firewalls. I deactivated advanced security with my ISP and opened ports 80, 443, 8888 and 999.

I get as far as getting to the player.htm screen and press “begin”. After that it just says please wait. Funny thing is that the Cirus out put says that I have connected.

I have not edited the config.js at all. Or anyother file except the Start_AWS_withTurn_SignalingServer file.

I followed this tutorial maybe five times.

Here is what my **Start_AWS_withTurn_SignalingServer file **contains

Copyright 1998-2018 Epic Games, Inc. All Rights Reserved.

$PublicIp = Invoke-WebRequest -Uri “http://169.254.169.254/latest/meta-data/public-ipv4”

Write-Output “Public IP: $PublicIp”

$peerConnectionOptions = “{ ““iceServers””: {”“urls”“: ““stun:” + $PublicIp + “:19302"”,”“turn:” + $PublicIp + “:19303"”], ““username””: ““PixelStreamingUser””, ““credential””: ““Another TURN in the road””}] }”

$ProcessExe = “node.exe”
$Arguments = @(“cirrus”, “–peerConnectionOptions=”“$peerConnectionOptions”“”, “–publicIp=$PublicIp”)

Add arguments passed to script to Arguments for executable

$Arguments += $args

Write-Output “Running: $ProcessExe $Arguments”
Start-Process -FilePath $ProcessExe -ArgumentList $Arguments -Wait -NoNewWindow

Here is the output from the Cirrus Console :

Cirrus.png
Cirrus.png1920×658 47.1 KB

2

Also I guess my real question is are the ports opened supposed to be TCP or UDP or does it matter? I did both

3

I have exactly the same issue! Would be great if someone could help.

Regards!

4

ok you need to open power shell or cmd and browse to “SignallingWebServer” folder like example “\WindowsNoEditor\Engine\Source\Programs\PixelStreaming\WebServers\SignallingWebServer” and type " npm audit " this will analyze the problem for your npm script and for me it gives me that i need to install “yargs@15.3.1” and “helmet@3.22.0” i installed them and i solve npm problem now i’m facing another issue that i can’t resolve tell know which is shown in photo any idea what is that …

5

To get *Invoke-WebRequest *work as intended you need to modify a script in *Start_AWS_withTurn_SignalingServer.ps1 *file, script provided by epic fails to retrieve public ip of the machine you are running your app from.

Simply remove this code


$PublicIp = Invoke-WebRequest -Uri "http://169.254.169.254/latest/meta-data/public-ipv4"

and instead paste this bit


$PublicIp = $(Resolve-DnsName -Name myip.opendns.com -Server 208.67.222.220).IPAddress

. Once launched it will return proper ip address of your machine, whether in cloud or in-house.

6

Thank you, no more red errors!

8

thx man this was useful but unfortunately still have unknowing issue this is my last update still have no connection

9

Hi asalia,

Have you opened the ports 80 and 8888 from your router?

I’m still having the exact same problem because of the ports, which even opened, are detected as closed, so I’m contacting with my ISP to solve this problem.

Regards!

10

Having the same issues. Checked my port 80 & 8888 and are open. Still no connection, only locally.

Help!

11

Everything is working fine locally, but once someone not on the same network tries to connect to the server, i get the following error in the webbrowser of the users logg

  • Websocket connection to ‘ws://80.xxx.x.xxx/’ failed: Connection closed before receiving a handshake respone.

The message to the user is “Starting connection to server, please wait”

Does anyone know what the problem is?
All ports are open and tested.
Correct parameters are on the streamer executeable correct and streamer is connected once its started.
The user makes it all the way until play is hit, and the errors above happend.

12

Have you gotten any further?
Im testing with 4.25 today to see any new results, but my last comment still stands.

13

ur a ■■■■■■■ god

14

My problem still persists, anyone? I have tried changing the publicIP line, still the same issue

15

I’m also still suffering from this. As localhost everything is working fine but when trying to use public ip, its just not working. Also, I open the ports from the router but when I check from online port checking tools, it says the ports are still closed… :frowning: Any suggestions??

16

I’m not sure if this is going to help you, but might as well give it a try. I never had any luck with the TURN server implementation that came packaged with PixelStreaming, so instead, I switched to Twillio (planning to test coturn in the future, but right now for testing, twillio is easier). You can install their CLI, and follow this tutorial Network Traversal Service | Twilio to generate your credentials for the turn server. Then just replace the turn server config in *start_aws_withturn_signalingserver.ps1 and hopefully it should be good. Careful though, Twillio is a paid service, so you will pay for the traffic(although it is very cheap, got a 15$ sign-up bonus, and I think I used 5$ in 2 months for testing)

Here is how my * start_aws_withturn_signalingserver.ps1 looks like this:



# Copyright 1998-2018 Epic Games, Inc. All Rights Reserved.

$PublicIp = Invoke-WebRequest -Uri "https://api.ipify.org/"

Write-Output "Public IP: $PublicIp"

$peerConnectionOptions = "{ \""iceServers\"": {\""urls\"": \""stun:global.stun.twilio.com:3478?transport=udp\"",\""turn:global.turn.twilio.com:3478?transport=udp\""], \""username\"": \""ebe1f116b4e113436583ff96efdc05540051599ba761d0815e7473\"", \""credential\"": \""mBtZqZ/oG+r9yRqWd24CXf0cJkQF3fJ8+OdGeGA=\""}] }"

$ProcessExe = "node.exe"
$Arguments = @("cirrus", "--peerConnectionOptions=""$peerConnectionOptions""", "--publicIp=$PublicIp")
# Add arguments passed to script to Arguments for executable
$Arguments += $args

Write-Output "Running: $ProcessExe $Arguments"
Start-Process -FilePath $ProcessExe -ArgumentList $Arguments -Wait -NoNewWindow

Edit1: About the ports, I had the same “problem” some time ago. Even if you open the ports, but you’re not running anything on them, the port checker will return that the port is closed (not 100% sure about this, I might be wrong, not an expert). But you can also make sure that the firewall is not an issue by completely disabling it ( do it just for testing, and don t forget to turn it back on again after). If with the firewall stopped, everything works, try and run this command in windows powershell :



New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol TCP -LocalPort 80
New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol TCP -LocalPort 19302-19303
New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol TCP -LocalPort 8888
New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol UDP -LocalPort 8888
New-NetFirewallRule -DisplayName 'UE4 Pixel Streamer' -Direction Inbound -Action Allow -Protocol UDP -LocalPort 19302-19303

Credits go to Kevin Ashman from amazon who did this amazing tutorial on how to deploy pixel streaming servers on was GitHub - aws-samples/deploying-unreal-engine-pixel-streaming-server-on-ec2: Repo contains code and documentation that allows you to deploy Windows-based Unreal Engine 4 Pixel Streaming builds to EC2.

17

Hello, if you’re reading this and still struggling I would just like to extend some of the solutions to the mistakes I made.

  1. Read the documentation again with a fresh view. The majority of the problems when I solved and looked over the documentation again, realised it had said that all along, apart from this next one.

  2. In the shortcut for the packaged unreal application you need to replace “localhost” with your public IP address in order for this to work across networks.

  3. In the runAWS_WithTURN file, you need to keep the “ \ ” at the end of the username and credential inputs

  4. If none of the public TURN and STUN servers are working go to
    “Engine/Source/ThirdParty/WebRTC/rev.23789/programs/Win64/VS2017/release” and run both the STUN/TURN server, the TURN server has the username and credentials set in the default “Start_AWS_WithTurn_SignalingServer”. Just type in your local IP in the “Start_AWS_TurnServer”.

  5. Twilio is a great option for a third party TURN/STUN server. The documentation is weird but straight forward and there aren’t a lot of tutorials out there for this particular purpose. However if you follow it exactly using the “Twilio-CLI” install part it will work fine.

  6. You can also set up “coturn” on a free linux EC2 with AWS, however personally I have not got this to work.

Good luck