search

roflcoopter / viseron

Self-hosted, local only NVR and AI Computer Vision software. With features such as object detection, motion detection, face recognition and more, it gives you the power to keep an eye on your home, office or any other place you want to monitor.
MIT License
1.5k stars 154 forks source link

VISERON: FFprobe could not connect to stream. Output: {'error': {'code': -111, 'string': 'Connection refused'}} #768

Open delfredd opened 2 weeks ago

delfredd commented 2 weeks ago

Hello, Can someone help me here:

I am having errors when I am trying to connect to my reolink cameras after configured on Viseron:

Viseron error

This is my configuration file:

Viseron Config.yaml.docx

thank you.

roflcoopter commented 2 weeks ago

Seems your camera is canceling the connection. Do you have any other software connected to the camera streams? Some cameras only allow a set number of open streams at any time

delfredd commented 2 weeks ago

Hi, roflcoopter Thanks for your help...In my network, I have 9 cameras, 6 integrated and monitored using Blue Iris. I am planning to migrate from Blue Iris to Viseron....., however, after reading your message, I fixed the configuration file trying to use two cameras that aren’t using any other software (Not connected through Blue Iris). I am still getting the same error. I don't know why I can't connect or why I am still having this error. I can't move on. Do you have any suggestions, please? Thanks!

roflcoopter commented 1 week ago

And you have no firewall in place that might block the connection?

delfredd commented 1 week ago

I am not using a firewall. but I can connect individually to a single camera through the IP address from any computer. The computer where I am configuring viseron is using Debian 12.

tms320 commented 1 week ago

I have the same problem:

[2024-06-19 20:55:05] [INFO    ] [viseron.components] - Setting up domain camera for component ffmpeg with identifier camera_2, attempt 2
[2024-06-19 20:55:05] [ERROR   ] [viseron.components.ffmpeg.stream.camera_2] - [tcp @ 0x5633778f70c0] Connection to tcp://10.42.0.139:554?timeout=0 failed: Connection refused
[2024-06-19 20:55:05] [ERROR   ] [viseron.components.ffmpeg.stream.camera_2] - rtsp://10.42.0.139:554/stream0: Connection refused
[2024-06-19 20:55:05] [ERROR   ] [viseron.components] - Domain camera for component ffmpeg is not ready. Retrying in 20 seconds. Error: FFprobe could not connect to stream. Output: {'error': {'code': -111, 'string': 'Connection refused'}}

Config of my camera:

    camera_2:  # This value has to be unique across all cameras
      name: Camera 2
      host: 10.42.0.139
      port: 554
      path: /stream0

I turned off authentification for RTSP stream, so there is no login/password. My network configuration:

image

Viseron installed on Debian 12 server. Server has two interfaces: wlo1 - main interface (wireless) connected to my main 'Network 1' via ISP-router. Camera 1 in this network works with Viseron without problems. The second ethernet interface 'enp2s0' is enslaved into network bridge using Network Manager:

image

Camera 2 connected to enp2s0 interface and has IP address 10.42.0.139. From inside Debian server I can ping both Camera 1 and Camera 2.