Jump to content

Bruceflix

Members
 View Profile  See their activity

  • Posts

    29

  • Joined

  • Last visited

 Content Type 

Posts posted by Bruceflix

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    2 hours ago, awediohead said:

     

     

    So

    1) Do I need to follow the instructions to Install the Edge TPU runtime on Unraid's console before I do anything else?

    2) Do I then need to install the PyCoral library?

    3) My USB coral never seems to initialise and change from 1a6e:089a Global Unichip Corp to Google Inc. - whats the quickest way of checking whether it's a factory dud?

     

    4) I thought I had created a very basic config.yml file just to get Frigate started so I could modify the config from within Frigate as is recommended - but with the USB Coral TPU plugged in starting Frigate up and looking at the logs, the logs window flickers for a fraction of a second and then disappears far too quickly to read anything. That said am I right in thinking I need to be seeing the device as Google Inc in lsusb before I can hope to launch Frigate successfully?

    ;)

    1) No

    2) No

    3) Mine shows as Google Inc. Probably thats enough to show that you have a dud.  I hope you purchased from an official store that has warranty. 

    • Thanks 1

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    3 minutes ago, Tarcisio said:

    Host seems to have the right config.
    Also -e TZ="America/Chicago" and   -v '/etc/localtime':'/etc/localtime':'rw' are already included by default in the docker run.

    image.png

    image.png

    I just re-read your initial problem and realized i've also got the same problem with the directory structure.  Frigate timezone is correct but the directory names are set to GMT. i think.

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    7 hours ago, danimal86 said:

    i'm not sure where to start with the docs.  

    https://docs.frigate.video/configuration/

     

    I recommend using vscode over notepad++

    and following from the documentation:
     

    VSCode Configuration Schema

    VSCode (and VSCode addon) supports the JSON schemas which will automatically validate the config. This can be added by adding # yaml-language-server: $schema=http://frigate_host:5000/api/config/schema.json to the top of the config file. frigate_host being the IP address of Frigate or ccab4aaf-frigate if running in the addon.

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    4 minutes ago, Lunch said:

     

    I've reinstalled my old Quadro p600 but cannot for the life of me see where I'm supposed to add it to the config file as well as the unraid docker template (assuming this needs to be done)....I'm Using Frigate 11

    For GPU detection you need to use Frigate 12

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    9 hours ago, Daniel Schneider said:

    Here is the link for the adapter from Github:

    https://github.com/magic-blue-smoke/Dual-Edge-TPU-Adapter

    I had a blackout the other day and I don't think my m2. coral and/or adaptor survived.  Coral crashes the whole server after a couple of minutes causing a server reboot. This is after months of uptime.

    Fortunately I have a spare USB coral to use.  Probably just order another adaptor to see exactly where the problem is.

    [SUPPORT] blakeblackshear - Frigate

    in Docker Containers

    Posted

    I think you need to read the documentation. The installation steps point out pretty clearly how to create the config.yml and what is needed in it.  I am not sure what configuration options you are expecting on a FOSS project.  Given the target demograph of Frigate is the HA community they would usually already be well versed in YAML.  

    Hey, if I can get it to work, anyone can.  

     

    [Support] IBRACORP - All images and files

    in Docker Containers

    Posted

    On 8/16/2022 at 4:19 PM, Rabbithacker921 said:

    i dont know if you figured out the answer yet, but for me it was just to add this before location in the advanced config in NPM

     

    port_in_redirect off;

     

    It will look like this 

     

    # Increase buffer size for large headers

    # This is needed only if you get 'upstream sent too big header while reading response

    # header from upstream' error when trying to access an application protected by goauthentik

    proxy_buffers 8 16k;

    proxy_buffer_size 32k;

    port_in_redirect off;

    location / {

    # Put your proxy_pass to your application here

    proxy_pass $forward_scheme://$server:$port;

    # authentik-specific config

    auth_request /outpost.goauthentik.io/auth/nginx;

    error_page 401 = @goauthentik_proxy_signin;

    auth_request_set $auth_cookie $upstream_http_set_cookie;

    add_header Set-Cookie $auth_cookie;

    # translate headers from the outposts back to the actual upstream

    auth_request_set $authentik_username $upstream_http_x_authentik_username;

    auth_request_set $authentik_groups $upstream_http_x_authentik_groups;

    auth_request_set $authentik_email $upstream_http_x_authentik_email;

    auth_request_set $authentik_name $upstream_http_x_authentik_name;

    auth_request_set $authentik_uid $upstream_http_x_authentik_uid;

    proxy_set_header X-authentik-username $authentik_username;

    proxy_set_header X-authentik-groups $authentik_groups;

    proxy_set_header X-authentik-email $authentik_email;

    proxy_set_header X-authentik-name $authentik_name;

    proxy_set_header X-authentik-uid $authentik_uid;

    }

    # all requests to /outpost.goauthentik.io must be accessible without authentication

    location /outpost.goauthentik.io {

    proxy_pass http://outpost.company:9000/outpost.goauthentik.io;

    # ensure the host of this vserver matches your external URL you've configured

    # in authentik

    proxy_set_header Host $host;

    proxy_set_header X-Original-URL $scheme://$http_host$request_uri;

    add_header Set-Cookie $auth_cookie;

    auth_request_set $auth_cookie $upstream_http_set_cookie;

    # required for POST requests to work

    proxy_pass_request_body off;

    proxy_set_header Content-Length "";

    }

    # Special location for when the /auth endpoint returns a 401,

    # redirect to the /start URL which initiates SSO

    location @goauthentik_proxy_signin {

    internal;

    add_header Set-Cookie $auth_cookie;

    return 302 /outpost.goauthentik.io/start?rd=$request_uri;

    # For domain level, use the below error_page to redirect to your authentik server with the full redirect path

    # return 302 https://authentik.company/outpost.goauthentik.io/start?rd=$scheme://$http_host$request_uri;

    }

     

    You sir, deserve a medal.

×
×
  • Create New...