yayitazale

I suspect that you have a problem with the IP assignment or the network, as you are not getting valid endpoints. You must see something like this in the WebUI:

I think the problem is the port, you have to declare it below the IP with the entry "port: 1884" (or just not declare it as you are using the default port), but maybe you have more things to fix. I suggest you for a easier start at the beginning to use the complete example config.yml example of the docs as a template: https://docs.frigate.video/configuration/index

Can you post the image of how are you configuring the container?

Witch status do you have on the webui?

As I assume that most of the people is using coral TPUs yes, it is a necessary concession. https://github.com/blakeblackshear/frigate/issues/165 https://github.com/blakeblackshear/frigate/issues/171 https://github.com/blakeblackshear/frigate/issues/325 I changed the template to not privileged mode as default in the past but most of the people complained about their TPUs not working and they are not use to change the docker deploy gui to advanced mode.

Enter to the containers console Install nano with "sudo apt install nano" Edit the jupyter_notebook_config.json file with "sudo nano /home/jupyter/.jupyter/jupyter_notebook_config.json" Add this entry to the file using a only numbers and letters token: "token": "YOUR_TOKEN" Save the file and restart the container In any case, I'm no t sure if this change will be preserved if I update the container.

Hi, I need help with Matomo container. I recently have some permission issues with unraid so I have launched the tools>new permissions under whole unraid. I have updated Matomo but now is unable to start and I'm getting this errors like: "rsync: [generator] chgrp "/bitnami/matomo/plugins/Widgetize/config/config.php" failed: Operation not permitted (1)" I tried to eliminate the container and copy the files to another folder to restart it with a fresh folder and then copy the config file but it doesn't start. Any clue how to chmod the folder? Thanks

As I see you are not using nvidia, so can you delete the extra parameter --gpus=all switching to the advanced view mode in there.

I was asking for a image of the container itself like so:

Ok I will change the template for not nvidia users and point it in the docs

Can you post your container config image?

Maybe you are having a issue related with this breaking change:

Are you pointing to the right path of config file? Are your port not allocated in another container?

Can you try to run it deleting the --gpus=all entry on extra parameters?