fmartinou

The [lscr.io](https://fleet.linuxserver.io/) API now claims for an authentication token from the Github registry 🤔 ``` $ curl -i https://lscr.io/v2/linuxserver/radarr/tags/list HTTP/2 401 date: Sat, 23 Jul 2022 09:30:00 GMT content-type: application/json...

Hi @lukasmrtvy , Your issue is a different one, I think. For GCR, because credentials are needed, the support for this registry isn't enabled by default. Have you configured the...

I've just found a solution... 🥳 Because lscr.io is only a proxy in front of the Github registry, you need to provide a [Github Personal Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) to make it work....

Please retry with a Github Personal token: [see here](https://fmartinou.github.io/whats-up-docker/#/configuration/registries/ghcr/?id=how-to-create-a-github-personal-token) I'm pretty sure that LinuxServer.io team has changed the visibility of their packages, which is the root of all these troubles.

Thank you for your feedback @alexdelprete :+1: The username + token are not mandatory to configure the GHCR integration because some images can be publicly accessed. Unfortunately, LinuxServer ones are...

In the latest `5.20.1`, LSCR is not automatically enabled anymore. It's still possible to enable **but** username/token is now mandatory.

Thanks for your feedback; it's fixed ([see commit here](https://github.com/fmartinou/whats-up-docker/commit/5876970c1b9887e3c519b063a32a2844672f13c1)). (waiting for Github to redeploy the static website)

Hi, "In theory", you can set up multiple triggers of the same type so you should be able to set one trigger per compose file. Something like ```yaml version: '3'...

Hi, Any errors in the logs at startup indicating if something went wrong when loading the configurations of the missing triggers?

``` 16:44:45.447 WARN whats-up-docker/registry: Some triggers failed to register (Error when registering component dockercompose ("file" is required)) ``` Some triggers seem not to be properly configured. For example, for Plex...