I updated to Discourse 2026.3.0-latest.1 (12b79c7da6) on Friday.
Ever since then, my admin page is showing:
Clicking through to the theme itself, I see Error cloning git repository, access is denied or repository is not found:
Same error for all of them.
The repos are all still publicly accessible, eg:
Might this be a bug in my latest update? 
I don’t know what is different but I just updated to 2026.3.0-latest.1 and followed your example and went to Admin→components→versatile banner and the component updated with out an error as in your example
Interesting.
I can wget the repo from the server itself so it doesn’t appear to be a blocking issue.
I’ll poke it some more and see what I can work out 
Sorry, to be clear, if I manually go in to each one and click “check for updates” then they do actually check for updates.
I’m not sure why they’re all showing an error prior to me manually checking each one.
oh, ok that is what I did
mine did not show that error prior though
like in your screen shot below, sorry I didn’t take a screen shot prior but that error message was not there as in below
I think I saw something similar on my forum in the past month, but everything worked fine later. Maybe there is some rate limiting by GitHub?
Have you tried a command line update?
I only ever updated via cmd line for the last eight years or so, I’ve never used the web interface 
How does the way of updating influence checking for theme updates?
I just thought about issues related to update failures when I saw your suggestion, but here the problem is encountering an issue with the connection to the Git repository when checking for updates, rather than during the update process, so it should be irrelevant to how the update is performed?
Simple suggestion as rebuilding from CMD line often fixes update issues. Sometimes I have even had to run rebuild twice to fix an issue.
It’s still there now, the list is shorter where I’ve manually clicked on a few of them today.
The “last checked” date is still incrementing but the error messages still persist, saying the repo can’t be accessed or found, yet it clearly can because I can click the “check for updates” button and it goes away.
Strange, no?
Given this is super hard to repro it feels like something related to your setup.
One idea I have here is just remove the component and re-add, maybe it was using an old url or something, maybe your droplet is being rate limited by github?
My money is on this, or on a GitHub outage. They have had a lot recently.
The timings might tie up with those outages reports too.
