Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

luci-app-keepalived: Unable to save contents: Permission denied #7685

Closed
1 task done
Jackie264 opened this issue Mar 18, 2025 · 3 comments · Fixed by #7688
Closed
1 task done

luci-app-keepalived: Unable to save contents: Permission denied #7685

Jackie264 opened this issue Mar 18, 2025 · 3 comments · Fixed by #7688

Comments

@Jackie264
Copy link

Is there an existing issue for this?

  • I have searched among all existing issues (including closed issues)

screenshots or captures

Image

Actual behaviour

Always shows "Unable to save contents: Permission denied"

Expected behaviour

Fix it, please.

Steps to reproduce

  1. go to Service --> VRRP --> Notification
  2. edit Keepalived.user
  3. Save & Apply

Additional Information

{
        "kernel": "6.6.73",
        "hostname": "Velop7C9",
        "system": "ARMv7 Processor rev 5 (v7l)",
        "model": "Linksys WHW03 V2 (Velop)",
        "board_name": "linksys,whw03v2",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.0",
                "revision": "r28427-6df0e3d02a",
                "target": "ipq40xx/generic",
                "description": "OpenWrt 24.10.0 r28427-6df0e3d02a",
                "builddate": "1738624177"
        }
}

What browsers do you see the problem on?

Safari

Relevant log output

@feckert
Copy link
Member

feckert commented Mar 19, 2025

I was able to reproduce that. I also saved a new content of keepalived.user.
However, a reload of the /etc/init.d/keepalived service then also issues the second message that access has been denied.
From my point of view, the /etc/init.d/keepalived service does not need to be restarted after changing the keepalived.user. I have opened a PR for this.

@Jackie264 Perhaps you can try this.

@Jackie264
Copy link
Author

I was able to reproduce that. I also saved a new content of keepalived.user. However, a reload of the /etc/init.d/keepalived service then also issues the second message that access has been denied. From my point of view, the /etc/init.d/keepalived service does not need to be restarted after changing the keepalived.user. I have opened a PR for this.

@Jackie264 Perhaps you can try this.

It works, thanks.

@feckert
Copy link
Member

feckert commented Mar 20, 2025

I have also backported this to the current stable branch openwrt-24.10 with 53679fd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants