I updated to Discourse 2026.3.0-latest.1 ( 12b79c7da6 ) on Friday. Ever since then, my admin page is showing: [Screenshot 2026-03-22 at 14.58.36] Clicking through to the theme itself, I see Error cloning git repository, access is denied or repository is not found: [Screenshot 2026-03-22 at 15.00…

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 [image]

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 :blush:

[imagem] Andrew_Rowe: and the component updated with out an error 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.

[imagem] Richie: if I manually go in to each one and click “check for updates” then they do actually check for updates. 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 …

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 :slight_smile:

[imagem] Heliosurge: Have you tried a command line update? 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.

[Discourse 2026.3.0-latest.1] Todos os temas reportando um erro de "Erro ao clonar repositório git, acesso negado ou repositório não encontrado"

Suporte

david (David Taylor) 23 Março , 2026 10:57 17

Minha aposta é nessa, ou em uma interrupção (outage) do GitHub. Eles têm tido muitas recentemente.

Tópico		Respostas	Vistas
Error cloning git repository, access is denied or repository is not found Development	11	1690	28 Fevereiro , 2020
Error cloning git repository, access is denied or repository is not found（theme) Support	8	301	30 Setembro , 2024
Themes/components from GitLab gives error 500 when installing/updating Bug	13	1428	5 Dezembro , 2022
Internal Server Error on theme update Support	7	774	15 Março , 2019
Can't upgrade because zip file theme marked as update on upgrade Bug	4	525	23 Julho , 2021

[Discourse 2026.3.0-latest.1] Todos os temas reportando um erro de "Erro ao clonar repositório git, acesso negado ou repositório não encontrado"

Related topics