No valid repository for https://github.com/home-assistant/addons

Oh joy, now supervisor has decided to remove the community addons on its own. I have no problem getting to either the hass io offical repository or the community repository on two different computers on my network, also on two different browsers.

21-03-24 22:36:24 INFO (MainThread) [supervisor.store.git] Cloning add-on https://github.com/hassio-addons/repository repository
21-03-24 22:36:24 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/hassio-addons/repository repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/hassio-addons/repository /data/addons/git/a0d7b954
  stderr: 'Cloning into '/data/addons/git/a0d7b954'...
fatal: unable to access 'https://github.com/hassio-addons/repository/': Failed to connect to github.com port 443: Connection refused
'.
21-03-24 22:36:24 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.FATAL_ERROR - ContextType.STORE / a0d7b954
21-03-24 22:36:24 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_REMOVE - ContextType.STORE / a0d7b954
21-03-24 22:36:24 INFO (MainThread) [supervisor.resolution.fixups.store_execute_remove] Remove invalid Store: a0d7b954
21-03-24 22:36:24 INFO (MainThread) [supervisor.store.git] Removing custom add-on repository https://github.com/hassio-addons/repository

Still the same problem…
What workaround can we try?

21-03-26 08:53:26 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
21-03-26 08:53:26 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-03-26 08:53:26 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-03-26 09:16:49 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached
21-03-26 10:53:26 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-03-26 10:53:26 INFO (MainThread) [supervisor.resolution.fixups.store_execute_remove] Remove invalid Store: core
21-03-26 10:53:26 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
21-03-26 10:53:26 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-03-26 10:53:26 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-03-26 11:50:05 WARNING (MainThread) [supervisor.store.git] No valid repository for https://github.com/home-assistant/addons
21-03-26 11:50:05 INFO (MainThread) [supervisor.store] Loading add-ons from store: 0 all - 0 new - 0 remove
21-03-26 11:50:05 INFO (MainThread) [supervisor.store] Loading add-ons from store: 0 all - 0 new - 0 remove

I had that part of the log indicating problems with the SSL certificate as well but from my experience it isn’t the problem as you can always include the url repository within the trusted websites trough the windows network configuration. If you do so and reboot the supervisor you’ll see that the SSL certificate log line goes away.

It is very strange, Still have the problem and I cannot install the deCONZ add on fo rthe COnbee2. So I cannot do anything…

Are we the only one with this problem? incredible

Yeap… it is a bit frustrating.
Isn’t there anyway to get supper programmers attention so they can help out amateurs as ourselves :stuck_out_tongue_winking_eye:??

I decided to jump somewhere else.
I am now on Debian 10, works like a charm.
With a snapshot should be very easy to keep everything in place.
Mine was a fresh installation so I didn’t have that issue at all.
Link guide for the brave.
Installing Home Assistant Supervised on a Raspberry Pi with Debian 10 - Community Guides - Home Assistant Community (home-assistant.io)

Not more than 30 minutes of effort, a lot of peace in the heart.

Hope devs can solve the problem anyway. It was a real nightmare being in the black hole.

1 Like

Yes! Just saw a video from a really nice guy that makes lots of demonstrations in regards of Home Assistant topics and apparently Hassio Supervised isn’t supported on ubuntu anymore…
In the following video he does a quite accurate walkthrough so you can follow, sorry it is in Spanish.

Hope he doesn’t mind me sharing over here:

Im gonna get my hands on it right know!
Good luck to u all.

i’ve been on debian before and the problem was still there…

omg really?

at the moment, it’s running healthy. hope it lasts :frowning:

I’ve tried to restart the supervisor from terminal and if i ask for info i see:

addons_repositories:  []

is this normal?
And i’ve enable the debug mode, now the log is:

21-03-27 18:09:38 INFO (MainThread) [__main__] Setting up Supervisor
21-03-27 18:09:42 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/hassio-addons/repository/ repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/hassio-addons/repository/ /data/addons/git/03b5fe11
  stderr: 'Cloning into '/data/addons/git/03b5fe11'...
fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com
'.
21-03-27 18:09:42 ERROR (MainThread) [supervisor.store] Can't load data from repository https://github.com/hassio-addons/repository/

From the supervisor log:

File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 100, in wrapper
    return await self._method(*args, **kwargs)
  File "/usr/src/supervisor/supervisor/store/git.py", line 195, in pull
    raise StoreGitError() from err
supervisor.exceptions.StoreGitError
21-03-28 09:09:45 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/addons/': Could not resolve host: github.com
'.
21-03-28 09:09:45 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
21-03-28 10:09:45 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/addons/': Could not resolve host: github.com
'.
21-03-28 10:09:45 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
21-03-28 11:09:45 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/addons/': Could not resolve host: github.com
'.
21-03-28 11:09:45 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!
21-03-28 12:09:44 ERROR (MainThread) [supervisor.store.git] Can't update https://github.com/home-assistant/addons repo: Reference at 'HEAD' does not exist.
21-03-28 12:09:44 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-25926' coro=<Repository.update() done, defined at /usr/src/supervisor/supervisor/store/repository.py:105> exception=StoreGitError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/store/git.py", line 152, in pull
    branch = self.repo.active_branch.name
  File "/usr/local/lib/python3.8/site-packages/git/repo/base.py", line 718, in active_branch
    return self.head.reference
  File "/usr/local/lib/python3.8/site-packages/git/refs/symbolic.py", line 270, in _get_reference
    sha, target_ref_path = self._get_ref_info(self.repo, self.path)
  File "/usr/local/lib/python3.8/site-packages/git/refs/symbolic.py", line 181, in _get_ref_info
    return cls._get_ref_info_helper(repo, ref_path)
  File "/usr/local/lib/python3.8/site-packages/git/refs/symbolic.py", line 164, in _get_ref_info_helper
    raise ValueError("Reference at %r does not exist" % ref_path)
ValueError: Reference at 'HEAD' does not exist
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/store/repository.py", line 109, in update
    await self.git.pull()
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 102, in wrapper
    raise err
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 100, in wrapper
    return await self._method(*args, **kwargs)
  File "/usr/src/supervisor/supervisor/store/git.py", line 195, in pull
    raise StoreGitError() from err
supervisor.exceptions.StoreGitError
21-03-28 12:09:45 ERROR (MainThread) [supervisor.store.git] Can't clone https://github.com/home-assistant/addons repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v https://github.com/home-assistant/addons /data/addons/core
  stderr: 'Cloning into '/data/addons/core'...
fatal: unable to access 'https://github.com/home-assistant/addons/': Could not resolve host: github.com
'.
21-03-28 12:09:45 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!

I have the same error. No add-on is shown too :frowning:

21-03-29 05:03:49 ERROR (MainThread) [supervisor.store.git] Can't clone http://github.com/hassio-addons/repository repository: Cmd('git') failed due to: exit code(128)
  cmdline: git clone --depth=1 --recursive --shallow-submodules -v http://github.com/hassio-addons/repository /data/addons/git/e399101c
  stderr: 'Cloning into '/data/addons/git/e399101c'...
fatal: unable to access 'http://github.com/hassio-addons/repository/': Could not resolve host: github.com
'.

I also have this error output:

21-03-29 05:45:26 ERROR (MainThread) [supervisor.store.repository] Can't remove built-in repositories!

And I had also a log indicating problems with the SSL certificate in the beginning.

Versions I used:

  • core-2021.3.4
  • supervisor-2021.03.6 + supervisor-2021.03.8
  • Home Assistant OS 5.12

i’ve tried to post the issue on github if you want to add some info: https://github.com/home-assistant/supervisor/issues/2774

I have the same problem :frowning:
no official add-ons (Home Assistant OS 5.12 64bit on Raspberry pi 4)

Thanks for the suggestion, I did it and it is working like a charm!!! really thanks!! And I can also use the terminal to install things and modify network settings as I am always in habit to do with linux!!!
Thanks, good suggestion

Hi ilceko,

Although I was exited to believe my problems were coming to an end thanks to this Debian 10 alternative, after a week of digging and traying commands (without a really specific knowledge on programming) i haven’t been able to set up and running Debian 10 yet…

Do you think you could give me a hand here?? I’m desperate, to the point that I might enrroll back into the university to sutdy informatics! :stuck_out_tongue:

The situations is that i am not able to install the update packages, being the very first step of the installation guide (Installing Home Assistant Supervised on a Raspberry Pi with Debian 10) when trying to update and install the OS packages. When runing the apt update and apt install the system returns:

Get:1 http://deb.debian.org/debian buster InRelease [121 kB]
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-backports InRelease [46.7 kB]
Reading package lists... Done
E: Release file for http://deb.debian.org/debian/dists/buster/InRelease is not valid yet (invalid for another 771d 23h 3min 35s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian-security/dists/buster/updates/Inelease is not valid yet (invalid for another 780d 0h 29min 41s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/buster-backports/InRelease is not valid yet (invalid for another 779d 21h 15min 25s). Updates for this repository will not be applied.

As I look up in different sources at the internet, it seems that the problem is related to a time syncronization, which in effect my system is not up to date:

root@rpi3-20210209:/home/noodi# timedatectl
               Local time: Thu 2019-02-14 11:51:44 CET
           Universal time: Thu 2019-02-14 10:51:44 UTC
                 RTC time: n/a
                Time zone: Europe/Madrid (CET, +0100)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
root@rpi3-20210209:/home/noodi# ^C
root@rpi3-20210209:/home/noodi#

From here i have tryied a bounch of options from different forums;

eg. https://www.digitalocean.com/community/tutorials/how-to-set-up-time-synchronization-on-debian-10

but no luck…

Most of them indicate me to install packages such as the ntp, chrony… but i can’t install any of them as the system always returns:

root@rpi3-20210209:/home/noodi# apt-get install chrony
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package chrony

Do you think you can give me a hand? Or should I have to claudicate and spend my money on apple’s homekit to automate my home? hhaahahha allow me some humor within this anoying situation.

Thanks in advance anyway for taking the time to read my missage :slight_smile:

For everyone who would like to try installing RPI + Debian 10 Supervised method then please try my scripts https://github.com/tirtadji-com/rpi_debian_ha_supervised

Let me know if it help

i think that the problem isn’t linked with debian, but some other issue!

i’ve update supervisor and core to the last versione but the issue persist…

sorry, I didn’t see you reply!
Did you get to solve?

The time/date issue is the same we have with broken hassio!

But moving to Debian my issue is solved. In your case seems still there.
Your router has correct time/date config?