deepch / RTSPtoWeb

RTSP Stream to WebBrowser
MIT License
1.27k stars 302 forks source link

Constantly restart with error flv: h264 seqhdr invalid #283

Closed GitHubCloud closed 1 year ago

GitHubCloud commented 1 year ago
INFO[2023-01-30T06:35:28Z] Server CORE start                             func=main module=main
INFO[2023-01-30T06:35:28Z] Server HTTP start                             call=Start func=RTSPServer module=http_server
INFO[2023-01-30T06:35:28Z] Server RTSP start                             call=Start func=RTSPServer module=rtsp_server
INFO[2023-01-30T06:35:28Z] Server start success a wait signals           func=main module=main
INFO[2023-01-30T06:35:28Z] Run stream                                    call=Run channel=0 func=StreamServerRunStreamDo module=core stream=27aec28e-6181-4753-9acd-0456a75f0289
ERRO[2023-01-30T06:35:30Z] Stream error restart stream flv: h264 seqhdr invalid  call=Restart
INFO[2023-01-30T06:35:32Z] Run stream                                    call=Run channel=0 func=StreamServerRunStreamDo module=core stream=27aec28e-6181-4753-9acd-0456a75f0289
ERRO[2023-01-30T06:35:36Z] Stream error restart stream flv: h264 seqhdr invalid  call=Restart
INFO[2023-01-30T06:35:38Z] Run stream                                    call=Run channel=0 func=StreamServerRunStreamDo module=core stream=27aec28e-6181-4753-9acd-0456a75f0289
ERRO[2023-01-30T06:35:43Z] Stream error restart stream flv: h264 seqhdr invalid  call=Restart
INFO[2023-01-30T06:35:45Z] Run stream                                    call=Run channel=0 func=StreamServerRunStreamDo module=core stream=27aec28e-6181-4753-9acd-0456a75f0289
ERRO[2023-01-30T06:35:49Z] Stream error restart stream flv: h264 seqhdr invalid  call=Restart

i've changed multiple environment: from MBP to CentOS, always getting this error. This is only command i've ran: docker run -itd --name rtsp2web --network host ghcr.io/deepch/rtsptoweb:latest

awdm commented 1 year ago

I'm having the same issue, did you manage to resolve it?

sahin52 commented 1 year ago

Same, is this a new problem?

awdm commented 1 year ago

I just build a Dockerfile from a version of the source code I pulled a while ago (don't know exactly when tho) and it runs fine, so it looks like this is indeed a new problem.

Edit: Running the library outside of Docker also produces the same error.

sahin52 commented 1 year ago

Why did you close the issue? Is there something we are missing? @GitHubCloud

GitHubCloud commented 1 year ago

@awdm @sahin52 You shouldn't use the default config.json file, it will load the default streams which is not available.

I use the example config.json file but empty the streams with blank, then it'll work.