Https-dns-proxy / curl: not found

https-dns-proxy: Starting service ✓✓✓
daemon.err uhttpd[2197]: sh: curl: not found

I think I found my DNS problem. DNS will begin to work for clients on the LAN if I disable 'https-dns-proxy'. Then if I re-enable https-dns-proxy, it remains working. odd.

I noticed in the system log that curl was missing.
The 'which curl' command didn't return any results. libcurl should have been installed as part of the package. Unless the log error is unrelated.

The https-dns-proxy does not require the curl itself. If you pay attention you'll notice that the error is coming from uhttpd, not https-dns-proxy, so you have to find out what changes have you made to your system that uhttpd suddenly complains about missing curl. Are you using a DynDNS package or manual dyndns solution?

Hi,
I too found this error in syslog when starting https-dns-proxy:

Thu May 18 12:57:15 2023 user.notice https-dns-proxy: Starting service ✓
Thu May 18 12:57:15 2023 daemon.err uhttpd[2051]: sh: curl: not found

Searching for why uhttpd wanted curl, I found curl here:
https://github.com/openwrt/luci/blob/master/applications/luci-app-https-dns-proxy/luasrc/model/cbi/https-dns-proxy.lua#L106

Could you please take a look and advise.
Thanks

2 Likes

Thanks, I'll make curl a dependency for WebUI at the next update. I don't want to touch the current WebUI code to properly fix it, due to the imminent rewrite of WebUI in javascript.

2 Likes

actually, @sqrwv @d687r02j8g do you mind testing luci-app-https-dns-proxy 2022-10-15-14 from my repo: https://github.com/stangri/repo.openwrt.melmac.net ?

I switched to just checking if the libnghttp2 is installed.

I installed the package using the ipk

I get the following error when I goto the Luci page

Runtime error
Unhandled exception during request dispatching
/usr/lib/lua/luci/ucodebridge.lua:23: /usr/lib/lua/luci/cbi.lua:53: /usr/lib/lua/luci/model/cbi/https-dns-proxy.lua:106: ')' expected near 'Provides'

In error(), file [C]
called from function [anonymous function] (/usr/lib/lua/luci/ucodebridge.lua:23)
called from function ((tail call))
In [anonymous function](), file /usr/share/ucode/luci/runtime.uc, line 148, byte 45:
  called from function [arrow function] (/usr/share/ucode/luci/dispatcher.uc:794:4)
  called from function render ([C])
  called from function render_action (/usr/share/ucode/luci/dispatcher.uc:768:24)
  called from function run_action (/usr/share/ucode/luci/dispatcher.uc:795:4)
  called from function [anonymous function] (/usr/share/ucode/luci/dispatcher.uc:998:48)
  called from anonymous function (/www/cgi-bin/luci:39:12)

 `        return lcall.call(modname, method, ...args);`
  Near here ----------------------------------------^

I am using a snapshot build - OpenWrt SNAPSHOT r22782-218ce40cd7 / LuCI Master git-23.118.79121-6fb185f

1 Like

Sorry, messed up my lua-fu :wink: Building a fixed IPK with the same version number now.

I get the error in system log about curl, but as far as I can tell, the package is working fine.

Which service is producing the curl error?

The curl error is gone here:

Thu May 18 23:45:20 2023 user.notice https-dns-proxy: Starting service ✓
Thu May 18 23:45:21 2023 daemon.info dnsmasq[1]: started, version 2.89 cachesize 3000
Thu May 18 23:45:21 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Thu May 18 23:45:21 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu May 18 23:45:21 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus

Thanks

3 Likes

This is using the package that's in the repo.

daemon.err uhttpd[3699]: sh: curl: not found

The error only occurs when visiting the services Luci page. The service itself seems to be fine.

Since luci-app-https-dns-proxy 2022-10-15-14 the WebUI doesn't call curl.

1 Like

I'm using luci-app-https-dns-proxy_2022-10-15-14_all.ipk and can't get the curl error no more, even when entering luci->services->https-dns-proxy.

Could it be your browser cache?

1 Like

Working now :ok_hand:

3 Likes