[Config Support]: QNAP Docker Compose - Bridge vs Host - Host Access Returns a 400 Bad Request ?

[nodecentral]

Describe the problem you are having

Hi, following the guidance online for installation with QNAP; I created an associated compose file which installed successfully via Container Station and is reporting to be up and running; however it did not seem to use the bridge facility and obtain an IP, but as I can see references to 127.0.0.1 in the log, so I assume it has tied itself to the host, so I’ve tried to access it via the host IP and the 8971 port, but it returns a 400 error ?

Version

ghcr.io/blakeblackshear/frigate:stable

Frigate config file

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    image: ghcr.io/blakeblackshear/frigate:stable
    network_mode: bridge
    shm_size: 256m 
    environment:
      - TZ:Europe/London
    working_dir: /opt/frigate
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /share/Container/frigate/config:/config
      - /share/Container/frigate/media:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      # - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    labels:
      - com.qnap.qcs.network.mode=nat
      - com.qnap.qcs.gpu=False
    deploy:
        resources:
            limits:
                memory: 4g
                cpus: “2”
    tty: true
    restart: unless-stopped

Relevant Frigate log output

Using Dozzle to monitor the logs and there are a huge amount of entries in there, if there is something specific I should look for (key word/phrase to search) please let me know.

Relevant go2rtc log output

Sorry not sure where to access this ?

Frigate stats

N/A

Operating system

Other Linux

Install method

Docker Compose

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[nodecentral]

Adding this other post for awareness as I thought it might be related - #11838 also hoping @RyanS027 RyanS027 who posted that might see this and provide any insight

[hawkeye217]

8971 is the https authenticated port. Are you accessing via https://...:8971 or just http://...?

[nodecentral]

Doh ! - yes that looks to be the issue, thanks - not sure why it would bounced me to http, when everything else is https. I can reach the login page now, however when it comes to logging in the guide its says..

On startup, an admin user and password are generated and printed in the logs. It is recommended to set a new password for the admin account after logging in for the first time under Settings > Users.

I’m scanning the logs via Dozzle but can’t see any mentioned of any admin account - what should I specifically be looking for ?

[hawkeye217]

The auto generated admin password will be displayed at the beginning of the logs on the first startup of frigate.

[nodecentral]

Perfect thanks so much @hawkeye217 - seems Dozzle only keeps the logs from the last restart, but was able to find it with the following command

docker logs frigate 2>&1 | grep "frigate.app.*INFO.*: \** "

[hawkeye217]

Great! Happy to help.