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
Exploit scanners hitting port 1935 can cause this:
[2024-04-06 12:44:12.584] I [SPRTMP-t1935:977208] Provider | stream.cpp:51 | Unknown/(105) has been started stream
[2024-04-06 12:44:12.585] I [SPRTMP-t1935:977208] RTMPProvider | rtmp_provider.cpp:194 | A RTMP client has connected from <ClientSocket: 0x7f1e67401210, #35, Connected, TCP, Nonblocking, 139.99.238.162:54674>
My RTMP port is protected with SignedPolicy of course. Maybe the log message is just wrong, but how can someone sending random data to port 1935 cause a stream to start?
The text was updated successfully, but these errors were encountered:
This does not mean that the RTMP stream has started, but simply indicates that someone has connected to the RTMP port, which is still in the Unknown state. (Before negotiation)
Exploit scanners hitting port 1935 can cause this:
My RTMP port is protected with SignedPolicy of course. Maybe the log message is just wrong, but how can someone sending random data to port 1935 cause a stream to start?
The text was updated successfully, but these errors were encountered: