Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ComplexHandshake error prevents OBS from pushing RTMP stream to SRSv3 #1034

Closed
objnf-dev opened this issue Dec 27, 2017 · 15 comments
Closed
Assignees
Labels
Bug It might be a bug. TransByAI Translated by AI/GPT.
Milestone

Comments

@objnf-dev
Copy link

objnf-dev commented Dec 27, 2017

Error occurred when using OBS to stream to SRS3. Make sure to maintain the markdown structure.

[2017-12-27 07:21:22.973][Trace][19][126] RTMP client ip=::ffff:172.17.0.2, fd=11
[2017-12-27 07:21:23.002][Trace][19][126] simple handshake success.
[2017-12-27 07:21:23.002][Error][19][126][11] connect error code=0 : rtmp handshake : complex handshake
thread #126: do_cycle() [src/app/srs_app_rtmp_conn.cpp:177][errno=11]
thread #126: handshake() [src/protocol/srs_rtmp_stack.cpp:2286][errno=11]
(Resource temporarily unavailable)

Tried binding the IPv4 address in OBS settings and disabling the IPv6 protocol in the client (Windows) network adapter properties. Both attempts were ineffective.
May there be any ways to fix it?

TRANS_BY_GPT3

@objnf-dev
Copy link
Author

objnf-dev commented Dec 27, 2017

OBS Studio error message box:

default

TRANS_BY_GPT3

@objnf-dev objnf-dev changed the title Unable to push RTMP stream using OBS Unable to push RTMP stream using OBS in SRS 3 Dec 27, 2017
@objnf-dev objnf-dev changed the title Unable to push RTMP stream using OBS in SRS 3 Unable to push RTMP stream using OBS to SRS v3 Dec 27, 2017
@objnf-dev
Copy link
Author

objnf-dev commented Dec 27, 2017

OBS Studio Log File:

16:17:16.523: ------------------------------------------------
16:17:17.920: ---------------------------------
16:17:17.920: [x264 encoder: 'simple_h264_stream'] preset: veryfast
16:17:18.108: [x264 encoder: 'simple_h264_stream'] settings:
16:17:18.108: 	rate_control: CBR
16:17:18.108: 	bitrate:      2500
16:17:18.108: 	buffer size:  2500
16:17:18.108: 	crf:          0
16:17:18.108: 	fps_num:      30
16:17:18.108: 	fps_den:      1
16:17:18.108: 	width:        1280
16:17:18.108: 	height:       720
16:17:18.108: 	keyint:       250
16:17:18.108: 
16:17:18.150: ---------------------------------
16:17:18.240: [FFmpeg aac encoder: 'simple_aac'] bitrate: 160, channels: 2
16:17:18.342: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://180.76.52.218/live...
16:17:18.342: [rtmp stream: 'simple_stream'] Binding to IPv4
16:17:18.344: [rtmp stream: 'simple_stream'] Interface: MAC Bridge Miniport (ethernet, 1000 mbps)
16:17:18.440: RTMPSockBuf_Fill, remote host closed connection
16:17:18.440: [rtmp stream: 'simple_stream'] Connection to rtmp://180.76.52.218/live failed: -3
16:17:18.441: ==== Streaming Stop ================================================

TRANS_BY_GPT3

@taozywu
Copy link

taozywu commented Dec 28, 2017

@zhouweitong3 Please set sercret. this sercret is random string.

at last uri like this 'rtmp://180.76.52.218/live/test', 'test' is your sercret.

good luck!

@objnf-dev
Copy link
Author

objnf-dev commented Dec 28, 2017

@taozywu has already set the stream name in OBS studio, the settings are as follows:
default

Still unable to push RTMP stream to SRS. The server keeps indicating that the source IP of the push is the IPv6 address of the SRS server.

TRANS_BY_GPT3

@man201601
Copy link

man201601 commented Dec 31, 2017

I discovered today that version 3.0 also has this issue, I don't know how to solve it!

TRANS_BY_GPT3

@man201601
Copy link

man201601 commented Dec 31, 2017

As follows, IPv6 is disabled.
tail -f objs/srs.log
[2017-12-31 20:39:10.615][Trace][3234][0] son(deamon) process running.
[2017-12-31 20:39:10.616][Trace][3234][0] st_init success, use epoll
[2017-12-31 20:39:10.616][Trace][3234][100] server main cid=100, pid=3234, ppid=1703, asprocess=0
[2017-12-31 20:39:10.616][Trace][3232][0] grandpa process exit.
[2017-12-31 20:39:10.616][Trace][3234][100] write pid=3234 to ./objs/srs.pid success!
[2017-12-31 20:39:10.620][Trace][3234][100] RTMP listen at tcp://0.0.0.0:1935, fd=8
[2017-12-31 20:39:10.622][Trace][3234][100] HTTP-API listen at tcp://0.0.0.0:1985, fd=9
[2017-12-31 20:39:10.624][Trace][3234][100] HTTP-Server listen at tcp://0.0.0.0:8080, fd=10
[2017-12-31 20:39:10.624][Trace][3234][100] signal installed, reload=1, reopen=10, grace_quit=15
[2017-12-31 20:39:10.625][Trace][3234][100] http: api mount /console to ./objs/nginx/html/console
[2017-12-31 20:39:37.593][Trace][3234][106] RTMP client ip=10.9.2.251, fd=11
[2017-12-31 20:39:37.593][Trace][3234][106] srand initialized the random.
[2017-12-31 20:39:37.594][Trace][3234][106] simple handshake success.
[2017-12-31 20:39:37.594][Error][3234][106][11] connect error code=0 : rtmp handshake : complex handshake
thread #106: do_cycle() [src/app/srs_app_rtmp_conn.cpp:177][errno=11]
thread #106: handshake() [src/protocol/srs_rtmp_stack.cpp:2286][errno=11]
(Resource temporarily unavailable)
^C
]# ss -tunl
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
tcp LISTEN 0 128 *:1985 :
tcp LISTEN 0 128 *:1935 :
tcp LISTEN 0 128 *:8080 :

TRANS_BY_GPT3

@man201601
Copy link

man201601 commented Dec 31, 2017

write pid=3300 to ./objs/srs.pid success!
[2017-12-31 20:58:52.398][trace][3300][100] RTMP listen at tcp://0.0.0.0:1935, fd=7
[2017-12-31 20:58:52.408][trace][3300][100] HTTP-Server listen at tcp://0.0.0.0:8080, fd=8
[2017-12-31 20:58:52.408][trace][3300][100] signal installed
[2017-12-31 20:58:52.419][trace][3300][100] http: api mount /console to /usr/local/nginx/html/console
[2017-12-31 20:58:52.429][trace][3300][100] ingest thread cid=104, current_cid=100
[2017-12-31 20:58:56.294][trace][3300][106] RTMP client ip=10.9.3.46
[2017-12-31 20:58:56.294][trace][3300][106] srand initialized the random.
[2017-12-31 20:58:56.295][trace][3300][106] simple handshake success. This is part of the 2.0 logs, pushing to obs 10.9.3.46. However, the displayed client is different!

TRANS_BY_GPT3

@man201601
Copy link

man201601 commented Dec 31, 2017

Is there any requirement for the gcc version during compilation?

TRANS_BY_GPT3

@PMExtra
Copy link

PMExtra commented Jan 11, 2018

+1

@objnf-dev objnf-dev changed the title Unable to push RTMP stream using OBS to SRS v3 IPv4/IPv6识别错误导致OBS无法推送RTMP流 Jan 22, 2018
@objnf-dev
Copy link
Author

objnf-dev commented Jan 22, 2018

Is there any solution?

TRANS_BY_GPT3

@wnpllrzodiac
Copy link
Contributor

wnpllrzodiac commented Jan 25, 2018

Is the end of the URL /?
Here, OBS Studio and SRS 2.0 work together smoothly.

TRANS_BY_GPT3

@objnf-dev
Copy link
Author

objnf-dev commented Jan 25, 2018

@wnpllrzodiac This is an issue with SRS3, version 2.0 does not have IPv6 functionality.

TRANS_BY_GPT3

@objnf-dev objnf-dev changed the title IPv4/IPv6识别错误导致OBS无法推送RTMP流 IPv4/IPv6识别错误导致OBS无法推送RTMP流至SRSv3 Jan 25, 2018
@winlinvip
Copy link
Member

winlinvip commented Feb 13, 2018

This problem is a bug introduced by changing from complex handshake to simple handshake. Even if the switch is successful, it will return a failure. Please refer to #1057. It has already been fixed.

TRANS_BY_GPT3

@winlinvip winlinvip added the Bug It might be a bug. label Feb 13, 2018
@winlinvip winlinvip added this to the srs 3.0 release milestone Feb 13, 2018
@winlinvip
Copy link
Member

winlinvip commented Feb 13, 2018

image

complex error accurately pointed out the location, it's not an IPv6 issue, ha.

TRANS_BY_GPT3

@objnf-dev
Copy link
Author

objnf-dev commented Feb 13, 2018

I thought at that time that "complex handshake" was indicating an IP error...
Thanks for the bug fix

TRANS_BY_GPT3

@winlinvip winlinvip self-assigned this Sep 12, 2021
@winlinvip winlinvip changed the title IPv4/IPv6识别错误导致OBS无法推送RTMP流至SRSv3 ComplexHandshake错误导致OBS无法推送RTMP流至SRSv3 Sep 12, 2021
@winlinvip winlinvip changed the title ComplexHandshake错误导致OBS无法推送RTMP流至SRSv3 ComplexHandshake error prevents OBS from pushing RTMP stream to SRSv3 Jul 27, 2023
@winlinvip winlinvip added the TransByAI Translated by AI/GPT. label Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug It might be a bug. TransByAI Translated by AI/GPT.
Projects
None yet
Development

No branches or pull requests

6 participants