Update ghcr.io/patchmon/patchmon-server Docker tag to v2.1.6
No problems upgrading the Docker container with a Docker compose yaml file by means of Watchtower DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot.
| Package | Update | Change |
|---|---|---|
| ghcr.io/patchmon/patchmon-server | patch | 2.1.4 → 2.1.6 |
Release Notes
PatchMon/PatchMon (ghcr.io/patchmon/patchmon-server)
v2.1.6: Version 2.1.6
A one-fix release: agents install and check in behind Traefik with the CrowdSec bouncer's AppSec enabled. This fix was listed in the 2.1.5 notes but missed that release.
Upgrading
docker compose pull
docker compose up -d
No database or configuration changes. The fix is in the agent: existing hosts receive it through agent auto-update (on at Settings > Agent Updates) at their next restart or daily full report, and new installs get it from the upgraded server.
Fixes
Agent install failed with a 403 behind Traefik and CrowdSec. Behind Traefik with the CrowdSec bouncer's AppSec enabled, the installer's connectivity test failed with ping request failed with status 403 and the agent service was never created. The agent's check-in carried no body length over HTTP/2, which the bouncer blocks by default. The agent now always sends one. Until your agents are updated, setting crowdsecAppsecUnreadableBodyBlock: false on the bouncer middleware works around it.
Every change in this release
| Issue | MR | Change |
|---|---|---|
| #1103 | #1180 | Agent install and check-in no longer fail with a 403 behind Traefik with the CrowdSec bouncer's AppSec over HTTP/2. |
What is coming next
Bug fixes are tracked in GitHub milestones. Feature requests live on feedback.patchmon.net, where you can propose an idea, vote on existing ones, and see what has been accepted onto the roadmap.
Questions about this release
This release has its own thread under New Release Discussions. Open a new issue for a reproducible bug not already covered.
v2.1.5: Version 2.1.5
A bug-fix release: patch validation works again when more than five packages are selected, validation on dnf and yum hosts lists the dependencies it would pull in, and the AI assistant's model lists are updated for providers retiring older models.
Upgrading
docker compose pull
docker compose up -d
No database or configuration changes.
The Traefik and CrowdSec agent fix shown in the in-app notes for this release ships in 2.1.6.
Fixes
Run validation did nothing. In 2.1.4, choosing Run validation in the patch wizard did nothing when any host had more than five packages selected, with no error shown. Validation now runs for any selection, as it did in 2.1.3, and Skip validation is always available.
Validation on Fedora, RHEL and Rocky hosts showed no dependencies. On hosts that use dnf or yum, a validation always said "No additional packages", even when the update would install or upgrade other packages alongside the ones you picked. The validation result now lists every package dnf would change, and flags the extra dependencies for review. Validations run before upgrading are not updated; run them again to see the full list.
AI assistant could not connect with a new Google Gemini key. Google now limits Gemini 2.5 to accounts that already used it, so a new key failed Test Connection on every listed model. The Gemini list now offers 3.5 Flash-Lite (the default), 3.6 Flash and 3.8 Flash. OpenAI's gpt-4-turbo and OpenRouter's google/gemini-2.5-flash are also retired, as both providers are switching them off this month. If you had a retired model saved, the assistant moves to that provider's default; existing Gemini 2.5 users keep their selection.
Every change in this release
| Issue | MR | Change |
|---|---|---|
| #1175 | #1179 | Run validation in the patch wizard did nothing when a host had more than five packages selected; it now validates any selection, as in 2.1.3. |
| #1179 | Validation on dnf and yum hosts now lists every package the update would install or upgrade, including dependencies, instead of none. | |
| #1174 | #1177 | AI assistant model lists updated: Gemini 3.5 Flash-Lite, 3.6 Flash and 3.8 Flash replace Gemini 2.5; retired OpenAI and OpenRouter models removed. |
What is coming next
Bug fixes are tracked in GitHub milestones. Feature requests live on feedback.patchmon.net, where you can propose an idea, vote on existing ones, and see what has been accepted onto the roadmap.
Questions about this release
This release has its own thread under New Release Discussions. Open a new issue for a reproducible bug not already covered.
