html5_rtsp_player icon indicating copy to clipboard operation
html5_rtsp_player copied to clipboard

[transport:ws] [ctrl] close. code: 4000 Invalid Domain (credentials)

Open wuzhoubo opened this issue 5 years ago • 9 comments

What is this code mean? this is the status in my server image

wuzhoubo avatar Mar 23 '19 06:03 wuzhoubo

the proxy server works well. You have added only ip address during activation of the free license. You didn't add the domain name. So test html page+player should be addressed and placed on ip that you wrote during activation.

victorgrenke avatar Mar 23 '19 08:03 victorgrenke

thx, But i don't know how to resolve it,my html page + player is in my server. this is the page http://47.92.212.1:8088/. help me.please

wuzhoubo avatar Mar 25 '19 03:03 wuzhoubo

my html page + player is in my server: 47.92.212.1

  • during activation write 47.92.212.1
  • open port 8088 to global
  • setup nginx if you use the same port for html and ws
  • write in test html page the link to your ws : ws://47.92.212.1:xxxx (xxxx=8088 if you right setup the webserver, if no open one more another port fro ws)
  • to watch test page try http://47.92.212.1:8088

victorgrenke avatar Mar 25 '19 04:03 victorgrenke

hope you change a little the your ip ^^

victorgrenke avatar Mar 25 '19 04:03 victorgrenke

thanks a lot, the demo rtsp (rtsp://184.72.239.149/vod/mp4:BigBuckBunny_175k.mov) could play in my server. But I had a new problem. It's the error code image My rtsp link is rtsp://111.85.177.122:554/pag://111.85.177.122:7302:002857:0:MAIN:TCP?cnid=100001&pnid=1&auth=50&streamform=rtp. It could play in my windows player.

wuzhoubo avatar Mar 25 '19 08:03 wuzhoubo

@wuzhoubo how do you solve invalid domain problem?

kuangch avatar Jun 10 '19 11:06 kuangch

WebSocket connection to 'wss://streamedian.com/ws/' failed: Error during WebSocket handshake: Unexpected response code: 502

sbzkp avatar Aug 25 '19 14:08 sbzkp

楼主是怎么解决的呀?能否告知一二

hupanfeng avatar Aug 30 '19 03:08 hupanfeng

When binding the address, fill in the address to access the application service, not the proxy server address. For example, my 192.168.1.100 has the application service deployed on it, and my 192.168.1.99 has the video proxy service deployed on it. Our application needs to access the RTSP stream address, so the address to be filled in when binding should be 192.168.1.100, not 192.0.0.99. The conclusion is that it restricts an activation code to bind only one domain name, and all services under this domain name can use this plug-in.

gaofeicm avatar Nov 16 '19 08:11 gaofeicm