If you have SSH & Web Terminal installed, type the following command:
wget https://github.com/hassio-addons/repository
If connection successful you should get:
Remove the file created with: rm repository
One more suggestion is to try 8.8.8.8 and/or 1.1.1.1 as the nameserver inside HA:
Setting → System → Network → IPv4
Did that - and here are the results - still no access to github/addon store:
resolution info
network info
- Unfortunately I could not install SSH because of missing access to addon store . another way to get this tested ?
- tried Cloudflare und Google in my previous attempts (see first post) with no success
Thanks you
There is no repairs under Settings → System → Repairs?
In HA CLI type: login
Then: curl https://github.com/hassio-addons/repository
You should either get an error if connection not possible or the contents of the repository file.
You can also use: curl https:///github.com/hassio-addons/repository | more to check contents which is a reference/list of .js add-on files.
It seems to be related to DNS issues.
I found a thread back from 2021 where an EERO network device is a culprit (around post 60 and down).
No repairs available
There’s no EERO or similar in use. Just my fritzbox as DSL modem. As an attempt I set it to “exposed host” to disable its firewall. unfortunately no success.
Have you tried this?
I answered at the bottom of my post no. 15.
I tried without success.
What happens if you ping 140.82.121.4 from the HA host?
What happens if you ping github.com from the HA host?
“login” works
and
curl GitHub - hassio-addons/repository: Home Assistant Community Add-ons works too.
No errors but a lot of stuff.
@WallyR
ping 140.82.121.4 brings “is alive!”
ping github.com brings “is alive!”
Could you try to install HAOS under Hyper-V in a Windows machine, then check if the add-on store issue persists?
Unfortunately I do not have a free bare metal machine to try that.
Would VirtualBox on Windows be an alternative ?
Or do I have to expect new issues with that ?
You can always check if the add-on store is visible there.
Unbelievable: on Virtualbox installed on a bare metal Windows 11 system it works like a charm. So “my” problem seems to lay on Proxmox.
How may this learning help me to identify the Proxmox issue ?
At least you now know it is not something on your network.
I can’t help with your proxmox issue, I used tteck’s script and I have no problems with the add-on store.
I found the reason !
In Proxmox the MTU size of the vmbr was set to 1464. After removing this entry the store was not empty anymore.
Thanks a lot for trying to help me.
1 Like
Just for future reference Hyper-V is part of Windows 10 and 11 and can be easily enabled in control panel → programs & features → turn windows features on/off → Hyper-V (it is installed as a type 2 hypervisor).
I was going to ask you to check Proxmox against my guide but I thought this would be too much to ask.
Glad you identified the issue.
Well, of course I checked your guide by installing my current system getting along with it. It works fine and covers all important aspects. The reason why I struggled was in my PVE configuration.