Test the Keel Web 19.0-3 template on your Proxmox VE and report #5

New issue

Open

opened 2026-10-03 10:59:09 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-10-03 10:59:09 -03:00

(Migrated from github.com)

Context
Keel Web is the web appliance (Nginx, with the Coraza WAF and Anubis installed but off in a simple installation), layered on Keel Core. The testing build Web 19.0-3 (step 10) is published as an LXC template for Proxmox VE, and we want reports from real Proxmox hosts.

What to do

Download the template and its checksum: https://github.com/Keel-Linux/keel-web/releases/tag/testing-19.0-3-step10-20261003
Check it: sha512sum -c debian-13-keel-web_19.0-3+step10-20261003_amd64.tar.zst.sha512
Copy the .tar.zst to your Proxmox template storage (for local: /var/lib/vz/template/cache/).
Create an unprivileged container (Debian OS type, nesting=1) on a test host, start it and go through the first-boot screens on the Proxmox Console.
Fill in this checklist in a comment on this issue:
- Proxmox VE version (pveversion), privileged or unprivileged
- First boot finished; which screens appeared
- http://[your-address]/ and https://[your-address]/ show the Keel default page (a browser warning about the self-signed certificate is expected)
- curl -sk -o /dev/null -w '%{http_code}\n' https://[your-address]/keel-health prints 204
- A missing page shows the Keel 404 page, with no Nginx version in it
- systemctl --failed output
- confconsole opens; the usage screen lists https:// addresses
- keel diff output
- Anything that says "TurnKey" where you expected "Keel" (check Keel-Linux/common#33 and Keel-Linux/keel#70 first)
Open a separate issue for each bug, in the repository it belongs to, and link it from your comment.

Done when
At least one complete checklist is posted here. A maintainer closes the issue once the build has enough reports.

Help
Ask in https://github.com/orgs/Keel-Linux/discussions

**Context** Keel Web is the web appliance (Nginx, with the Coraza WAF and Anubis installed but off in a simple installation), layered on Keel Core. The testing build Web 19.0-3 (step 10) is published as an LXC template for Proxmox VE, and we want reports from real Proxmox hosts. **What to do** 1. Download the template and its checksum: https://github.com/Keel-Linux/keel-web/releases/tag/testing-19.0-3-step10-20261003 2. Check it: `sha512sum -c debian-13-keel-web_19.0-3+step10-20261003_amd64.tar.zst.sha512` 3. Copy the `.tar.zst` to your Proxmox template storage (for `local`: `/var/lib/vz/template/cache/`). 4. Create an unprivileged container (Debian OS type, `nesting=1`) on a test host, start it and go through the first-boot screens on the Proxmox Console. 5. Fill in this checklist in a comment on this issue: - [ ] Proxmox VE version (`pveversion`), privileged or unprivileged - [ ] First boot finished; which screens appeared - [ ] `http://[your-address]/` and `https://[your-address]/` show the Keel default page (a browser warning about the self-signed certificate is expected) - [ ] `curl -sk -o /dev/null -w '%{http_code}\n' https://[your-address]/keel-health` prints `204` - [ ] A missing page shows the Keel 404 page, with no Nginx version in it - [ ] `systemctl --failed` output - [ ] `confconsole` opens; the usage screen lists `https://` addresses - [ ] `keel diff` output - [ ] Anything that says "TurnKey" where you expected "Keel" (check Keel-Linux/common#33 and Keel-Linux/keel#70 first) 6. Open a separate issue for each bug, in the repository it belongs to, and link it from your comment. **Done when** At least one complete checklist is posted here. A maintainer closes the issue once the build has enough reports. **Help** Ask in https://github.com/orgs/Keel-Linux/discussions