luci-app-ocserv: "Disconnect" button on status page does nothing - OpenWRT 25.12.2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.9k
- Forks
- 2.9k
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 28
Description
Is there an existing issue for this?
- I have searched among all existing issues (including closed issues)
screenshots or captures
luci-app-ocserv 26.117.61665~4764bf4
Actual behaviour
Clicking the "Disconnect" button produces message that the connected user is being disconnected, however no actual disconnect happens.
Expected behaviour
Disconnect the user when pressing the "Disconnect" button.
Steps to reproduce
Connect user to the OpenConnect server running on OpenWRT 25.12.5, go to the status page and press "Disconnect" to force disconnect, message appears but the connection stays active.
Additional Information
{
"kernel": "6.12.74",
"hostname": "OpenWrt",
"system": "ARMv7 Processor rev 1 (v7l)",
"model": "Linksys WRT1900ACS",
"board_name": "linksys,wrt1900acs",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "25.12.2",
"firmware_url": "https://downloads.openwrt.org/",
"revision": "r32802-f505120278",
"target": "mvebu/cortexa9",
"description": "OpenWrt 25.12.2 r32802-f505120278",
"builddate": "1774469393"
}
}
What browsers do you see the problem on?
Firefox
Relevant log output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the luci-app-ocserv status page and reproduce the issue with an active OpenConnect user on OpenWrt 25.12.2. Trace the Disconnect button action from the page through the LuCI request to determine where the successful-looking message diverges from the server state. Done means pressing Disconnect actually ends the user's connection while preserving correct status feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100