why is there no https-dns-proxy package in release 24.10.1?
There is.
Did you update the package lists?
opkg update
opkg list | grep https-dns-proxy
opkg update
opkg install https-dns-proxy
I get..
Unknown package 'https-dns-proxy'.
Collected errors:
- opkg_install_cmd: Cannot install package https-dns-proxy.
Let’s see the complete output:
ubus call system board
opkg update
opkg install https-dns-proxy
look at this
root@OpenWrt:~# ubus call system board
{
"kernel": "6.6.86",
"hostname": "OpenWrt",
"system": "MediaTek MT7628AN ver:1 eco:2",
"model": "Xiaomi Mi Router 4C",
"board_name": "xiaomi,mi-router-4c",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.1",
"revision": "r28597-0425664679",
"target": "ramips/mt76x8",
"description": "OpenWrt 24.10.1 r28597-0425664679",
"builddate": "1744562312"
}
}
root@OpenWrt:~# opkg update
Downloading https://downloads.openwrt.org/releases/24.10.1/targets/ramips/mt76x8 /packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading https://downloads.openwrt.org/releases/24.10.1/targets/ramips/mt76x8 /packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ base/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_base
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ base/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/targets/ramips/mt76x8 /kmods/6.6.86-1-78926a92b8005e1b08d7e47b6d51efc0/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_kmods
Downloading https://downloads.openwrt.org/releases/24.10.1/targets/ramips/mt76x8 /kmods/6.6.86-1-78926a92b8005e1b08d7e47b6d51efc0/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ luci/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_luci
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ luci/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ routing/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_routing
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ routing/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_telephony
Downloading https://downloads.openwrt.org/releases/24.10.1/packages/mipsel_24kc/ telephony/Packages.sig
Signature check passed.
root@OpenWrt:~# opkg install https-dns-proxy
Unknown package 'https-dns-proxy'.
Collected errors:
* opkg_install_cmd: Cannot install package https-dns-proxy.
root@OpenWrt:~# root@OpenWrt:~# ubus call system board
-ash: root@OpenWrt:~#: not found
It may be a target build thing. I see it on my pi4, but that uses a completely different target. It’s possible the build had an issue with the package for that target. Or sometimes the build bots rebuild packages and it is just a waiting game for it to finish.
Try again tomorrow and see if it resolves.
I think someone should fix it
otherwise tomorrow will be the same
"someone" doesn't owe you anything, roll up your sleeves or wait, perhaps longer than until tomorrow ...
thank you! This was very valuable information for me...
hahahaha
it wasn't meant to be informative, but you're welcome anyway 
reason for it missing is linked to from Owut: https-dns-proxy: Package build failures affect this device: details at https://downloads.openwrt.org/releases/faillogs-24.10/mipsel_24kc/
1 Like
Oh hey, thanks for linking me.
Gosh, I could learn how to do it. I'd love to contribute, but I'm not sure how to go about it.
I'm good at logic and I can fumble my way through making scripts.
If I had to guess, and I'm saying to be redirected, but it seems that it's a CI/CD automation thing that led to this error, but I'm not really sure how the bot messed it up or if it's even something that I could fix with a pull request or what. It just seems like something that will get fixed on another pass as build bot comes around for another scan--kind of like how when there's a new OpenWRT build and it takes a few days to loop over all of the targets and packages.
Is that right? How would I have been able to contribute if at all?
no worries, just wanted to show OP where to find the reason for it missing.
the failure isn't related to openwrt or the package, but DNS name resolution:
fatal: unable to access 'https://github.com/aarond10/https_dns_proxy/': Could not resolve host: github.com
1 Like
fatal: unable to access 'https://github.com/aarond10/https_dns_proxy/': Could not resolve host: github.com
Oh, DNS. Yeah, that just needs another pass. Kind of ironic given the nature of the package.
I wonder if it'll try again later or if someone has to manually trigger it again.
Ah, haha, nice. We went over it nearly the same time. It appears that you beat me to it though