question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Config Support]: Outgoing Traffic is too heavy

See original GitHub issue

Describe the problem you are having

Outgoing Traffic is too heavy. Frigate is not being accessed externally. I am using a VPS and docker. https://ibb.co/gMrBywD

Version

0.11.1-2EADA21

Frigate config file

mqtt:
  host: 191.0.0.0
  user: admin
  password: ---

#Birdeyes Global
birdseye:
  enabled: False
  mode: continuous

# Global FFMPEG
# ffmpeg:
#   hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p

# #Tentativa Xeon
# ffmpeg:
#   hwaccel_args: -c:v h264_qsv

# Global Record
record:
  enabled: True
  retain:
    days: 0
  events:
   # Optional: Number of seconds before the event to include (default: shown below)
    pre_capture: 5
    # Optional: Number of seconds after the event to include (default: shown below)
    post_capture: 5
    retain:
      default: 1
      mode: active_objects

# Global Objects
objects:
  track:
    - person
    - car
    - motorcycle
    - dog
  filters:
    person:
      threshold: 0.6
    car:
      threshold: 0.6
    motorcycle:
      threshold: 0.6
    dog:
      threshold: 0.6
#Global Detect
detect:
  width: 352 # <---- update for your camera's resolution
  height: 240 
  fps: 5
  stationary:
    interval: 0
    threshold: 100

#Global Snapshot
snapshots:
  enabled: True
#   clean_copy: False
#   crop: True
#   enabled: True
#   bounding_box: True
#   retain:
#     default: 1

#Cameras
cameras:

#CAMERA GARAGEM
  001_garagem:
    ffmpeg:
      inputs:
        - path: rtsp://admin:password@ip/cam/realmonitor?channel=2&subtype=1 # <----- Update for your camera
          roles:
            - detect
            # - rtmp
            # - record
        # - path: rtsp://admin:password@ip/cam/realmonitor?channel=2&subtype=0 # <----- Update for your camera
        #   roles:
        #     - record
    motion:
      mask:
        - 352,0,352,29,182,28,182,0
    record:
      events:
        required_zones:
          - 001_zn_garagem
    snapshots:
      required_zones:
        - 001_zn_garagem
    zones:
      001_zn_garagem:
        coordinates: 0,240,352,240,352,114,327,99,240,99,113,45,0,50


#CAMERA FRENTE
  001_frente:
    ffmpeg:
      inputs:
        - path: rtsp://admin:password@ip/cam/realmonitor?channel=1&subtype=1 # <----- Update for your camera
          roles:
            - detect
            # - rtmp
            # - record
        # - path: rtsp://admin:password@ip/cam/realmonitor?channel=1&subtype=0 # <----- Update for your camera
        #   roles:
        #     - record
    record:
      events:
        required_zones:
          - 001_zn_entrada
    snapshots:
      required_zones:
        - 001_zn_entrada
    motion:
      mask:
        - 352,0,352,94,0,138,0,0
    zones:
      001_zn_entrada:
        coordinates: 146,171,0,175,0,240,352,240,352,208,323,158,293,94,221,97,151,109
    objects:
      filters:
        motorcycle:
          max_area: 22000    
          mask:
            - 352,0,352,88,235,102,222,156,0,175,0,0
        car:
          max_area: 40000     
          mask:
            - 352,0,352,88,235,102,222,156,0,175,0,0
        person:
          min_area: 4000
          max_area: 18000
          mask:
            - 0,0,352,0,352,96,0,142


 # CAMERA LATERAL           
  001_lateral:
    ffmpeg:
      inputs:
        - path: rtsp://admin:password@ip/cam/realmonitor?channel=3&subtype=1 # <----- Update for your camera
          roles:
            - detect
            # - rtmp
            # - record 
        # - path: rtsp://admin:password@ip/cam/realmonitor?channel=3&subtype=0 # <----- Update for your camera
        #   roles:
        #     - record           
    motion:
      mask:
        - 352,0,352,27,187,27,185,0
    objects:
      track:
        - person
        - dog
      filters:
        person:
          mask:
            - 300,42,275,161,206,131,217,36
    snapshots:
      required_zones:
        - 001_zn_lateral
    record:
      events:
        required_zones:
          - 001_zn_lateral
    zones:
      001_zn_lateral:
        coordinates: 67,64,290,240,0,240,0,99

Relevant log output

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2022-11-29 19:18:20] frigate.app                    INFO    : Starting Frigate (0.11.1-2eada21)
Starting migrations
[2022-11-29 19:18:20] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2022-11-29 19:18:20] peewee_migrate                 INFO    : There is nothing to migrate
[2022-11-29 19:18:20] frigate.app                    INFO    : Output process started: 212
[2022-11-29 19:18:20] frigate.app                    INFO    : Camera processor started for 001_garagem: 214
[2022-11-29 19:18:21] frigate.app                    INFO    : Camera processor started for 001_frente: 215
[2022-11-29 19:18:21] frigate.app                    INFO    : Camera processor started for 001_lateral: 216
[2022-11-29 19:18:21] ws4py                          INFO    : Using epoll
[2022-11-29 19:18:21] frigate.app                    INFO    : Capture process started for 001_garagem: 221
[2022-11-29 19:18:21] frigate.app                    INFO    : Capture process started for 001_frente: 222
[2022-11-29 19:18:21] detector.cpu                   INFO    : Starting detection process: 211
[2022-11-29 19:18:21] frigate.edgetpu                WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2022-11-29 19:18:21] frigate.app                    INFO    : Capture process started for 001_lateral: 225
[2022-11-29 19:18:22] ws4py                          INFO    : Using epoll
[2022-11-29 19:18:23] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:58134]
[2022-11-29 19:19:26] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:58134]

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

Coral version

CPU (no coral)

Any other information that may be helpful

EDIT No response

Issue Analytics

  • State:open
  • Created 10 months ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
NickM-27commented, Nov 29, 2022

it’s difficult to know what is incoming and outgoing in the context. for example my NAS shows this: Screen Shot 2022-11-29 at 12 49 29 PM

and “outgoing” just means any data sent to from the NAS (running frigate) to any other device on the network. Frigate does not communicate with anything outside of the local network except through reverse proxies that the user sets up.

0reactions
dipiexcommented, Nov 29, 2022

If MQTT is on a different device then that could very well be it. In any case you can try disabling the device running frigate’s WAN connection to see if it will continue using it, but I th

Frigate, Mosquitto and Hass are in separated docker containers ate the same VPS. I am gonna try some tests. Thank you Nick.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Firewall Best Practices - Egress Traffic Filtering
Rigorous logging of denied outbound connections could help identify scofflaws that are either ignorant or defiant of your AUP, as well as provide...
Read more >
Inbound vs. outbound firewall rules: What are the differences?
Outbound firewall rules protect against outgoing traffic, such as requests to questionable or dangerous websites, VPN connections and email services, ...
Read more >
Configuring Windows Firewall and Network Access Protection
Lesson 1: Configuring Windows Firewall. Windows Firewall filters incoming traffic to help block unwanted network traffic.
Read more >
VPC firewall rules - Google Cloud
Each firewall rule applies to incoming (ingress) or outgoing (egress) connections, not both. For more information, see direction of connection. Firewall rules ...
Read more >
Block connections to your Mac with a firewall - Apple Support
On your Mac, choose Apple menu > System Settings, click Network in the sidebar, then click Firewall. (You may need to scroll down.)....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found