luci-app-coovachilli: wrong UCI config name causes RPC error

Open Beginner friendly
#8,955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript
Domain
backend, frontend

Research direction

Start with /www/luci-static/resources/view/coovachilli/coovachilli.js and /usr/share/rpcd/acl.d/luci-app-coovachilli.json, then compare their UCI configuration name with /etc/config/chilli and the listed uci and ubus commands. Verify that the LuCI page requests the existing chilli configuration, loads without the RPCError, and retains the required RPC access.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched among all existing issues (including closed issues)
screenshots or captures

On OpenWrt 25.12.5, the CoovaChilli LuCI page fails with:

RPCError
RPC call to uci/get failed with ubus code 4: Resource not found

Installed versions:

OpenWrt 25.12.5 r33051-f5dae5ece4
coova-chilli-1.7-r1
luci-app-coovachilli-26.230.68036~04ab59d

The CoovaChilli backend uses:

/etc/config/chilli

and these commands work correctly:

uci show chilli
ubus call uci get '{"config":"chilli"}'

However, the LuCI application uses:

new form.Map('coovachilli', ...)

and the rpcd ACL also grants access to:

"uci": [ "coovachilli" ]

The browser therefore requests:

{"config":"coovachilli"}

which does not exist.

Changing both references from coovachilli to chilli fixes the problem and the LuCI page loads correctly.

So the LuCI frontend seems to be using a different UCI config name than the coova-chilli backend package.

Actual behaviour

Opening Services → CoovaChilli in LuCI fails with the following error:

RPCError
RPC call to uci/get failed with ubus code 4: Resource not found

The browser RPC request shows that LuCI is trying to access the UCI configuration "coovachilli":

{"config":"coovachilli"}

However, the coova-chilli package uses /etc/config/chilli.

The backend itself is working correctly. Both commands below return the expected configuration:

uci show chilli
ubus call uci get '{"config":"chilli"}'

I found that luci-app-coovachilli uses "coovachilli" in both the form.Map() definition and the rpcd ACL.

Changing these references from "coovachilli" to "chilli" fixes the issue and the LuCI page loads normally.

Expected behaviour

The CoovaChilli LuCI page should load normally and use the existing "chilli" UCI configuration provided by the coova-chilli package (/etc/config/chilli).

Steps to reproduce
  1. Install coova-chilli and luci-app-coovachilli.

  2. Open LuCI.

  3. Navigate to Services → CoovaChilli.

  4. The page fails with:

    RPCError
    RPC call to uci/get failed with ubus code 4: Resource not found

  5. Verify that the actual backend configuration exists and works:

    uci show chilli
    ubus call uci get '{"config":"chilli"}'

  6. Inspect the LuCI RPC request. It attempts to access:

    {"config":"coovachilli"}

    instead of:

    {"config":"chilli"}

  7. Change the UCI configuration name in luci-app-coovachilli from "coovachilli" to "chilli" in:

    /www/luci-static/resources/view/coovachilli/coovachilli.js

    and:

    /usr/share/rpcd/acl.d/luci-app-coovachilli.json

  8. Restart rpcd/uhttpd and reload LuCI.

  9. The CoovaChilli page now loads correctly.

Additional Information
{
        "kernel": "6.12.94",
        "hostname": "OpenWrt",
        "system": "ARMv7 Processor rev 1 (v7l)",
        "model": "Linksys WRT32X",
        "board_name": "linksys,wrt32x",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "25.12.5",
                "firmware_url": "https://downloads.openwrt.org/",
                "revision": "r33051-f5dae5ece4",
                "target": "mvebu/cortexa9",
                "description": "OpenWrt 25.12.5 r33051-f5dae5ece4",
                "builddate": "1782737960"
        }
}
What browsers do you see the problem on?

Microsoft Edge

Relevant log output
RPCError
RPC call to uci/get failed with ubus code 4: Resource not found
  at ClassConstructor.handleCallReply (http://192.0.0.2/luci-static/resources/rpc.js?v=26.228.64776~6a1e10b-1787152619:15:3)

Relevant RPC request captured in the browser developer tools:

{"jsonrpc":"2.0","id":5,"method":"call","params":["<session-id>","uci","get",{"config":"coovachilli"}]}
Dominant language
JavaScript
Stars
7.9k
Forks
2.9k
Avg merge
4d 5h
Merged PRs (30d)
30

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openwrt/luci

All issues in openwrt/luci

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.