Unable to connect to server - Websocket connection to server failed

[Jaj]

I have a trial version of WCS installed on an Amazon EC2 instance running Ubuntu 18 (Not through the marketplace)
Letsencrypt SSL installed
Server working fine with all the demos running as expected
port 8443 open (Screenshot attached)
Server listening on 8443 (Again, screenshot attached)

When I try to test embedd one of your examples (https://flashphoner.com/embedding-webcam-broadcasting-in-a-browser-to-a-web-page-2/) on one of our development server, it cannot seem to connect with the WCS server. I have attached a screenshot of the browser console. The page can be tested here - https://dev.syncline.in/wcstest/

Any help would be appreciated... Thank you

 

[Max]

Hello

Try

wss://studio.streaminglive.in:8443 instead of wss://studio.streaminglive.in

If you do not set port in the wss URL, port 443 is assumed.

 

[Jaj]

Thanks Max,
That worked!!

Also having trouble with REST API requests..
https://studio.streaminglive.in:9091/rest-api/push/startup gives me

The requested URL can't be reached
The service might be temporarily down or it may have moved permanently to a new web address.

Cannot read property 'tcp' of undefined

Any pointers to what I am missing would really help..

 

[Max]

Also having trouble with REST API requests..
https://studio.streaminglive.in:9091/rest-api/push/startup gives me

Please check if TCP port 9091 is opened
Also, this is not HTTPS port, so you have to use HTTP URL http://studio.streaminglive.in:9091/rest-api/push/startup

 

[Jaj]

Hi Max,

Port is open (Screenshot attached)
Strangely, still throws up the same error (Screenshot attached)

 

[Max]

We've tested. REST API seems to be working:

Please check ports accessibility from your PC to server using this method

 

[Jaj]

Thank you so much for your time Max, but I am all confused now...
Tried a different Rest API extension, for firefox this time and I get a 500 Internal error...

 

[Max]

rtmpurl field is incorrect. Case sensitive.
should be rtmpUrl

 

[Jaj]

Sorry, corrected that, but the results seem to be the same...

However, the interesting part is that if I POST the same thing to port 8888 it executes without a response..

 

[Max]

You have to pass header

Content-Type: application/json

 

[Jaj]

Tried everything possible! Cant figure out how it works for you...

 

[Max]

Works fine using another REST client

Double check

POST

http://studio.streaminglive.in:8081/rest-api/push/startup

Content-Type: application/json

{
"rtmpUrl": "rtmp://localhost:1935/live",
"streamName": "test"
}

 

[Jaj]

Figured it out, It had to do with the quotes that I was posting.
Everything working fine now.

Thanks a Ton for all your support Max, Much appreciated!!