当使用FFmpeg推送RTMP流时,可能会出现”Cannot read RTMP handshake response”的错误。这通常是由于防火墙或代理服务器等网络问题导致的。 以下是一些可能解决此错误的步骤: 确保RTMP服务器地址正确并且可以连接。尝试使用ping命令测试服务器是否可达。 禁用防火墙或添加例外规则以允许RTMP流传输。请注意,不同操作系统和防...
然后确认和云端转推地址(nginx-rtmp)通联,首先Ping IP,没问题,再用telnetIP 端口测试,发现通联没问题 再在本地用ffmpeg推流本地的摄像头到云端,没问题 复制推流命令采用命令推流,失败 在推流命令ffmpeg后面加上 -v debug参数 ,可以看到Cannot read RTMP handshake response,在RTMP握手过程出现了问题,导致连接被重置 ...
I can start Nginx without any error. but when run ffmpeg -f avfoundation -framerate 30 -i "1:0" -f flv rtmp://34.212.9.178/live for testing stream server, I got error message as following Cannot read RTMP handshake response rtmp://34.212.9.178/live: Connection reset by peer What is ...
Sign in Sign up ltebean/LivePublic Notifications Fork418 Star2.4k Code Issues21 Pull requests1 Actions Projects Security Insights New issue Jump to bottom Open Kristaps89opened this issueSep 1, 2017· 0 comments Open Cannot read RTMP handshake response.#35 ...
在推流命令ffmpeg后面加上 -v debug参数 ,可以看到Cannot read RTMP handshake response,在RTMP握手过程出现了问题,导致连接被重置 那么就只可能是网络问题,很有可能是现场配置了网络策略,导致握手无法完成 打电话与现场网络工程师沟通确认配置了新的网络策略,开放白名单,再次测试可以正常推流,问题解决。
[113] complex handshake success [2019-11-30 06:24:32.979][Trace][1][113] connect app, tcUrl=rtmp://172.17.0.2/video, pageUrl=, swfUrl=, schema=rtmp, vhost=172.17.0.2, port=1935, app=video, args=(obj) [2019-11-30 06:24:32.979][Trace][1][113] edge-srs ip=172.17.0.2, ...
== Info: schannel: sent initial handshake data: sent 77 bytes == Info: schannel: SSL/TLS connection with github.com port 443 (step 2/3) == Info: schannel: failed to receive handshake, need more data == Info: schannel: SSL/TLS connection with github.com port 443 (step 2/3) == ...