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
and I use this command to run SRS in docker docker run --rm -it -p 1935:1935 -p 8090:8090 -p 8000:8000 --env CANDIDATE=* -p 10080:10080/udp -v d:/share/:/usr/local/srs/objs/nginx/html/share/ registry.cn-hangzhou.aliyuncs.com/ossrs/srs:5 ./objs/srs -c objs/nginx/html/share/docker.conf
I tested docker images like ossrs/srs:5 5.0.210(Bee) and ossrs/srs:v6.0-d6 6.0.134(Hang), and both of them have the same error.
I also tested docker image ossrs/srs:v5.0.60 which can access to http web site, but can not play webrtc stream.
When use different ports, then all runs well.
The text was updated successfully, but these errors were encountered:
chkzack
changed the title
Webrtc over tcp use same port with Http Server and Http Api
Webrtc over tcp use same port with Http Server and Http Api will cause http unavaiable
Jul 19, 2024
chkzack
changed the title
Webrtc over tcp use same port with Http Server and Http Api will cause http unavaiable
Webrtc over tcp use same port with Http Server and Http Api will cause http site unavailable
Jul 19, 2024
When I use same port with Http Server and Http Api to use Webrtc over tcp, reference to WebRTC over TCP, will cause http site unavailable.
Here is the error:
Here is the settings I used:
and I use this command to run SRS in docker
docker run --rm -it -p 1935:1935 -p 8090:8090 -p 8000:8000 --env CANDIDATE=* -p 10080:10080/udp -v d:/share/:/usr/local/srs/objs/nginx/html/share/ registry.cn-hangzhou.aliyuncs.com/ossrs/srs:5 ./objs/srs -c objs/nginx/html/share/docker.conf
I tested docker images like
ossrs/srs:5 5.0.210(Bee)
andossrs/srs:v6.0-d6 6.0.134(Hang)
, and both of them have the same error.I also tested docker image
ossrs/srs:v5.0.60
which can access to http web site, but can not play webrtc stream.When use different ports, then all runs well.
The text was updated successfully, but these errors were encountered: