All Projects

IDCategoryTask TypePrioritySeveritySummaryReported InStatus
3359PackagesBug ReportVery LowMediumhttps-dns-proxy / luci-app-https-dns-proxy: expose a co...TrunkUnconfirmed Task Description

As per, it supports `-v` for `Increase logging verbosity. (INFO)`. I’m encountering some problems with https-dns-proxy ( but I can’t troubleshoot them because there’s no way to pass `-v` to `https-dns-proxy` when started by luci-app-https-dns-proxy.

3357PackagesBug ReportVery LowLowcollectd-mod-openvpn: can't enable pluginTrunkUnconfirmed Task Description

See the screenshot. Unlike other plugins, this one is missing “Enable this plugin” checkbox, and therefore, cannot be enabled via UI.

3356PackagesBug ReportVery LowMediumhttps-dns-proxy: Luci interface breaks the configuratio...openwrt-19.07Unconfirmed Task Description

When you edit `/etc/config/https-dns-proxy` and set a custom server, not known to Luci HTML interface, the Luci UI at /cgi-bin/luci/admin/services/https-dns-proxy will display “CIRA Canadian Shield (Family)” as the selected resolver. This, by itself is not a problem yet, as the Proxy will function as expected.

However, the moment one makes any changes in the UI, e.g. changing listen port, `/etc/config/https-dns-proxy` will get rewritten and an actual resolver for CIRA Canadian Shield (Family) will be used.

Luci interface for HTTPS DNS Proxy should:

1. Bare minimum: indicate a custom resolver is used, and not lose the resolver after making changes to listen port and other stuff.
1. Nice to have: Allow a user to define a custom resolver in the UI - by specifying `resolver_url`, `bootstrap_dns`, `user` and `group` properties

The problem applies on any device as it’s not device-specific.

Reproduction instruction:

1. Edit `/etc/config/https-dns-proxy` and make it look like this:

config main ‘config’

      option update_dnsmasq_config '-'

config https-dns-proxy

      option listen_addr ''
      option listen_port '5054'
      option user 'nobody'
      option group 'nogroup'
      option bootstrap_dns ',,2606:4700:4700::1111,2606:4700:4700::1001'
      option resolver_url ''

2. Go to and observe “CIRA Canadian Shield (Family)” as the selected resolver.
3. Change listen port and click Save & Apply.
4. Observe `/etc/config/https-dns-proxy` lose `resolver_url` setting.

Showing tasks 1 - 3 of 3 Page 1 of 1

Available keyboard shortcuts


Task Details

Task Editing