Hello,
I have EC2 windows machine, where I’ve UE5 with pixel streaming and WebSignallingServer, the problem is that whenever I try to connect with secure web socket from the custom Frontend that I have set up on another machine, it is not letting me. I have tried launching WebSignallingServer with https, proxying Frontend/Backend server to this EC2 machine, now it works in these cases:
- When accessing wss url via Postman, it is connecting and exchanging data
- When going directly to the proxied url, meaning https://myurl.com/pixelstream (this is an example), if I go here, I see the frontend that UE has by default for pixel streaming
I’m using the latest pixel streaming library in my custom frontend application.
If anyone’s ever encountered the similar problem and knows how to resolve or debug it, the help will be much appreciated. If something is not clear, feel free to shoot questions.
This got approved a bit late and in the meantime I found solutions/workarounds, so here they are:
- Ngrok: launch WebSignallingServer (no need for https), launch .exe of ngrok, authenticate and then launch it with the suggestion that it gives, it’ll show public https url and you can use it to access ps (including socket itself) from anywhere.
- Route 53: launch WebSignallingServer with https config. You’ll need certificate, self signed one should work as well I think, otherwise just safely copy your current domain’s certificates there and paste them in the certificates folder, you’ll need cert and key pem files and you should be able to access it through your sub domain.
Both of these fixes are pretty much the same under the hood, but main thing is that it’s working.