WebRTC: The interface can be requested and returns normally, but it cannot be played using Google Chrome browser and SRS live streaming app. It keeps spinning in circles. #2148
Assignees
Labels
Milestone
Comments
Is /live/livestream being occupied by another stream? Try using a different stream.
|
|
Big boss, is it resolved?
|
|
|
Solved, thank you very much.
------------------ Original Email ------------------
Sender: "ossrs/srs" ***@***.***;
Sent: March 31, 2021 (Wednesday) 11:39 PM
***@***.***>;
***@***.******@***.***>;
Subject: Re: [ossrs/srs] Unable to play webrtc (#2148)
Boss, is it resolved?
The problem has been resolved, but I forgot the specific solution. You can refer to the two configurations below.
`
listen 1935;
max_connections 1000;
daemon off;
srs_log_tank console;
http_server {
enabled on;
listen 8080;
}
http_api {
enabled on;
listen 1985;
}
rtc_server {
enabled on;
listen 8000;
candidate $CANDIDATE;
}
vhost defaultVhost {
rtc {
enabled on;
bframe discard;
}
http_remux { enabled on; mount [vhost]/[app]/[stream].flv; } tcp_nodelay on min_latency on; play { gop_cache off; queue_length 10; mw_latency 100; } publish { mr off; }
}
`
`
listen 1935;
max_connections 1000;
srs_log_file ./objs/srs.log;
http_server {
enabled on;
listen 8080;
dir ./objs/nginx/html;
https {
enabled on;
listen 8088;
key ./conf/zhibo_server.key;
cert ./conf/zhibo_server.crt;
}
}
http_api {
enabled on;
listen 1985;
https {
enabled on;
listen 1990;
key ./conf/zhibo_server.key;
cert ./conf/zhibo_server.crt;
}
}
stats {
network 0;
}
rtc_server {
enabled on;
# Listen at udp://8000
listen 8000;
#
# The $CANDIDATE means fetch from env, if not configed, use * as default.
#
# The * means retrieving server IP automatically, from all network interfaces,
# @see #307 (comment)
candidate 81.68.105.42;#$CANDIDATE;
ecdsa on;
encrypt on;
merge_nalus off;
}
vhost defaultVhost {
rtc {
enabled on;
bframe discard;
stun_timeout 30;
stun_strict_check on;
dtls_role passive;
dtls_version auto;
drop_for_pt 0;
}
http_remux {
enabled on;
mount [vhost]/[app]/[stream].flv;
hstrs on;
}
tcp_nodelay on min_latency off; play { gop_cache off; queue_length 10; mw_latency 0; mw_msgs 1; } publish { mr off; }
}
`
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
`TRANS_BY_GPT3`
|
|
rtc_server {
|
|
@x-batman 👍 +1 |
|
How to solve the crash well, changing the configuration doesn't work.
|
winlinvip
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description'
Please ensure that the markdown structure is maintained.
4.0.59Please make sure to maintain the markdown structure.
Please make sure to maintain the markdown structure.
Replay
Please make sure to maintain the markdown structure.
How to replay bug?
Please make sure to maintain the markdown structure.
xxxxxxxxxxxxxxxxxxExpected behavior (Expect)
Please make sure to maintain the markdown structure.
Make sure to maintain the markdown structure.
TRANS_BY_GPT3The text was updated successfully, but these errors were encountered: