Some time during the 25th the Docker update check function stopped working for images hosted on GHCR, other repositories like Gitlab seems to work fine. 
I'm inclined to think that this is due to some change done by GitHub, but automations using the same method to authenticate seems to still work, which brings my suspicion back to Unraid.

I can confirm this.

My docker update also fails with ghcr images.

This is still happening. Any new development?

😐

I see the same, pretty annoying

Wonder why there is respond to this ?

Seems like it's being ignored.

@Squid is this something you could help with?

As @limetech stated,

 

 

 

 

I did open up a issue a couple of days ago on an internal bug tracker

6 minutes ago, Squid said:

I did open up a issue a couple of days ago on an internal bug tracker

 

Thanks for the quick response.

 

I guess I'm used to companies that charge money (and even ones that don't) for their products, would have at least given an acknowledgment after several days. Let's see when a response and a fix is published.

That being said, when I checked this out a couple of days ago, my test install of JellyFin (hotio) on ghcr after a check for updates did say "Not Available".  Today it is saying up to date for me after a check for updates

Can anyone help me reproduce the problem? This is what I've done so far in Unraid 6.9.1:

• go to CA, search for "jellyfin hotio"
• click to install, choose "release-ghcr"
• install
• go to the docker tab, it shows "up-to-date"
• click "check for updates", it shows "up-to-date"

1 hour ago, ljm42 said:

Can anyone help me reproduce the problem? This is what I've done so far in Unraid 6.9.1:

• go to CA, search for "jellyfin hotio"
• click to install, choose "release-ghcr"
• install
• go to the docker tab, it shows "up-to-date"
• click "check for updates", it shows "up-to-date"

At the time of the original posting, it was saying "Not Available", and tracing out the dockerMan code revealed Token errors.  As of today, it is returning "Up To Date", so I think the problem is fixed (by docker / gitHub themselves), but no one posted in response to my implied question which was the same as yours.

I did see it behave like it should a few minutes after Squid replied with his success, I just wanted to wait a few hours to confirm. It does look solved, I would say. 

As for the cause, all the token stuff worked everywhere else I use them, so its a mystery to me.