gabrielchaparro
New Member
Hello,
I've been trying to stream over RTMPS into a custom built media server, it uses custom port 4443 and does receive RTMPS from other similar devices perfectly, however when pushing RTMPS from OBS it is rejected as "invalid certificate" the log say:
OBS Log:
15:26:42.421: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://dme329gabriel.lab.vbrick.com:4443/live...
15:26:42.427: [rtmp stream: 'simple_stream'] Interface: Cisco AnyConnect Virtual Miniport Adapter for Windows x64 (type 0, 582↓/582↑ mbps)
15:26:42.427: [rtmp stream: 'simple_stream'] Interface has non-zero error counters (0/24 errors, 0/0 discards)
15:26:42.494: RTMP_Connect1, Cert verify failed: 8 (The certificate is not correctly signed by the trusted CA)
15:26:42.494: [rtmp stream: 'simple_stream'] Connection to rtmps://dme329gabriel.lab.vbrick.com:4443/live failed: -2
15:26:42.494: ==== Streaming Stop ================================================
Media server log:
2023-08-14@17:20:10::3:/thelib/src/protocols/ssl/inboundsslprotocol.cpp:101:InitGlobalContext:Apply cipher suite `HIGH:!ADH:!MD5:!RC4:!SRP:!PSK:!DSS` on inboundRtmps :::4443
2023-08-14@17:20:10::3:/thelib/src/protocols/ssl/inboundsslprotocol.cpp:113:InitGlobalContext:SSL server context initialized
2023-08-14@17:20:10::3:/thelib/src/netio/epoll/tcpacceptor.cpp:222:Accept:Inbound connection accepted: (Far: ::ffff:10.120.0.254:63107; Near: ::ffff:10.10.5.152:4443) CTCP(14) <-> TCP(5) <-> ISSL(6) <-> [IRS(7)]
2023-08-14@17:20:10::0:/thelib/src/netio/epoll/tcpcarrier.cpp:98:OnEvent:Unable to read data from connection: (Far: ::ffff:10.120.0.254:63107; Near: ::ffff:10.10.5.152:4443) CTCP(14) <-> [TCP(5)] <-> ISSL(6) <-> IRS(7). Error was (104): Connection reset by peer
is there any restriction when using non-standard ports?
After checking for solutions in this OBS forum I've tried all the posted solutions, all unsuccessfully.
Verified that PC and media server have perfectly synced NTP time.
Both PC and the media server can push into YouTube and Facebook successfully.
My PC (and many of other people's PCs) does have the Go Daddy Root Certificate Authority - G2 certificate installed.
Microsoft Edge (and all browsers) does access perfectly the device over regular HTTPS port 443.
Tried with Windows 10 fully updated, Windows 11 Pro 10.0.22621 with all the current available updates, although we've been having this issue for several months.
OBS 29.1.3 (64-bit, windows)
I've been trying to stream over RTMPS into a custom built media server, it uses custom port 4443 and does receive RTMPS from other similar devices perfectly, however when pushing RTMPS from OBS it is rejected as "invalid certificate" the log say:
OBS Log:
15:26:42.421: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://dme329gabriel.lab.vbrick.com:4443/live...
15:26:42.427: [rtmp stream: 'simple_stream'] Interface: Cisco AnyConnect Virtual Miniport Adapter for Windows x64 (type 0, 582↓/582↑ mbps)
15:26:42.427: [rtmp stream: 'simple_stream'] Interface has non-zero error counters (0/24 errors, 0/0 discards)
15:26:42.494: RTMP_Connect1, Cert verify failed: 8 (The certificate is not correctly signed by the trusted CA)
15:26:42.494: [rtmp stream: 'simple_stream'] Connection to rtmps://dme329gabriel.lab.vbrick.com:4443/live failed: -2
15:26:42.494: ==== Streaming Stop ================================================
Media server log:
2023-08-14@17:20:10::3:/thelib/src/protocols/ssl/inboundsslprotocol.cpp:101:InitGlobalContext:Apply cipher suite `HIGH:!ADH:!MD5:!RC4:!SRP:!PSK:!DSS` on inboundRtmps :::4443
2023-08-14@17:20:10::3:/thelib/src/protocols/ssl/inboundsslprotocol.cpp:113:InitGlobalContext:SSL server context initialized
2023-08-14@17:20:10::3:/thelib/src/netio/epoll/tcpacceptor.cpp:222:Accept:Inbound connection accepted: (Far: ::ffff:10.120.0.254:63107; Near: ::ffff:10.10.5.152:4443) CTCP(14) <-> TCP(5) <-> ISSL(6) <-> [IRS(7)]
2023-08-14@17:20:10::0:/thelib/src/netio/epoll/tcpcarrier.cpp:98:OnEvent:Unable to read data from connection: (Far: ::ffff:10.120.0.254:63107; Near: ::ffff:10.10.5.152:4443) CTCP(14) <-> [TCP(5)] <-> ISSL(6) <-> IRS(7). Error was (104): Connection reset by peer
is there any restriction when using non-standard ports?
After checking for solutions in this OBS forum I've tried all the posted solutions, all unsuccessfully.
Verified that PC and media server have perfectly synced NTP time.
Both PC and the media server can push into YouTube and Facebook successfully.
My PC (and many of other people's PCs) does have the Go Daddy Root Certificate Authority - G2 certificate installed.
Microsoft Edge (and all browsers) does access perfectly the device over regular HTTPS port 443.
Tried with Windows 10 fully updated, Windows 11 Pro 10.0.22621 with all the current available updates, although we've been having this issue for several months.
OBS 29.1.3 (64-bit, windows)
Last edited: