[Support]: Port 5000 Connection Refused #12313

chrisoflaherty · 2024-07-05T19:39:08Z

chrisoflaherty
Jul 5, 2024

Describe the problem you are having

I'm trying to run Frigate in Proxmox using Docker LXC. I'm not too sure what I've done wrong, but I cannot get the Frigate container to connect to the network for viewing of the security cameras.

When I restart the container, it shows the ports that it is trying to connect to, but when I try to reach the webpage, the IP Address and Published Ports go blank. There's also a message for connection refused for port 5000 in the Container health section.

In the "Container health" section the last output I am seeing is:

curl: (7) Failed to connect to 127.0.0.1 port 5000: Connection refused

Version

NA

Frigate config file

mqtt:
  enabled: false
ffmpeg:
  hwaccel_args: preset-vaapi
#Global Object Settings
objects:
  track:
    - person
  filters:
    person:
      min_area: 5000
      max_area: 100000
cameras:
  FrontCam:
    ffmpeg:
      inputs:
        # High Resolution Stream
        - path: rtsp:https://USERNAME:[email protected]:544/Streaming/Channels/101
          roles:
            - record
        # Low Resolution Stream
        - path: rtsp:https://USERNAME:[email protected]:544/Streaming/Channels/102
          roles:
            - detect
    detect:
      width: 480
      height: 360
      fps: 24

Relevant log output

2024-07-05 12:56:07.900611644  12:56:07.900 INF [webrtc] listen addr=:8555
2024-07-05 12:56:08.545724986  [Errno 30] Read-only file system: '/config/model_cache'
2024-07-05 12:56:08.710756100  [INFO] Service Frigate exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-05 12:56:08.719188812  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-05 12:56:08.746579245  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2024-07-05 12:56:08.748581093  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
2024-07-05 12:56:08.751548404  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service frigate-log successfully stopped
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-07-05 12:56:14.553391462  [INFO] Preparing Frigate...
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-07-05 12:56:14.559079082  [INFO] Starting NGINX...
2024-07-05 12:56:14.560205680  [INFO] Preparing new go2rtc config...
2024-07-05 12:56:14.566615091  [INFO] Starting Frigate...
s6-rc: info: service legacy-services successfully started
2024-07-05 12:56:14.763581915  [INFO] Starting go2rtc...
2024-07-05 12:56:14.832117789  12:56:14.832 INF go2rtc version 1.8.4 linux/amd64
2024-07-05 12:56:14.832679309  12:56:14.832 INF [api] listen addr=:1984
2024-07-05 12:56:14.833031882  12:56:14.833 INF [rtsp] listen addr=:8554
2024-07-05 12:56:14.833323495  12:56:14.833 INF [webrtc] listen addr=:8555
2024-07-05 12:56:15.452245438  [Errno 30] Read-only file system: '/config/model_cache'
2024-07-05 12:56:15.618938554  [INFO] Service Frigate exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-05 12:56:15.624422427  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-05 12:56:15.656798359  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2024-07-05 12:56:15.660425210  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-07-05 12:56:15.663194244  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

FFprobe output from your camera

ffprobe version 5.1.5-0+deb12u1 Copyright (c) 2007-2024 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-14)
  configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
Input #0, rtsp, from 'rtsp:https://USERNAME:[email protected]:554/Streaming/Channels/101':
  Metadata:
    title           : Media Presentation
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: h264 (Main), yuvj420p(pc, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 15 fps, 15 tbr, 90k tbn
  Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s

Frigate stats

No response

Operating system

Proxmox

Install method

Docker Compose

Object Detector

CPU (no coral)

Network connection

Wired

Camera make and model

ANNKE C800

Any other information that may be helpful

I'm pretty sure this is the latest version of frigate but I cannot open the web ui to find out for certain.

Any help would be greatly appreciated, as I am new to trying frigate, and I am trying to understand how this works.

Thanks!

Answered by hawkeye217

Jul 5, 2024

Frigate isn't running, which is why you get a "connection refused" error.

You'll want to fix this error and restart the container:

2024-07-05 12:56:15.452245438  [Errno 30] Read-only file system: '/config/model_cache'

View full answer

hawkeye217 · 2024-07-05T19:41:58Z

hawkeye217
Jul 5, 2024
Collaborator

Frigate isn't running, which is why you get a "connection refused" error.

You'll want to fix this error and restart the container:

2024-07-05 12:56:15.452245438  [Errno 30] Read-only file system: '/config/model_cache'

3 replies

chrisoflaherty Jul 5, 2024
Author

Wow, I can't believe I missed that line. Thank you for the help!

awilliams84 Jul 7, 2024

Wow, I can't believe I missed that line. Thank you for the help!

how did you fix this? I am running into the same issue, but I don't see the file

awilliams84 Jul 7, 2024

nevermind... figured it out! It was an issue in docker compose because I was following this: https://www.youtube.com/watch?v=DmbFq5dMsFo

volumes: - /opt/frigate/config:/config:ro

should be

volumes: - /opt/frigate/config:/config

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: Port 5000 Connection Refused #12313

{{title}}

Replies: 1 comment 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

[Support]: Port 5000 Connection Refused #12313

chrisoflaherty Jul 5, 2024

Describe the problem you are having

Version

Frigate config file

Relevant log output

FFprobe output from your camera

Frigate stats

Operating system

Install method

Object Detector

Network connection

Camera make and model

Any other information that may be helpful

Replies: 1 comment · 3 replies

hawkeye217 Jul 5, 2024 Collaborator

chrisoflaherty Jul 5, 2024 Author

awilliams84 Jul 7, 2024

awilliams84 Jul 7, 2024

chrisoflaherty
Jul 5, 2024

Replies: 1 comment 3 replies

hawkeye217
Jul 5, 2024
Collaborator

chrisoflaherty Jul 5, 2024
Author