Repository navigation
Bug: nginx sites-enabled/autobot-slm diverged from sites-available — client_max_body_size missing #1122
Description
Problem
/etc/nginx/sites-enabled/autobot-slm on .19 is a standalone file (not a symlink to sites-available), last modified Feb 20 14:54. The sites-available version has client_max_body_size 10m; added in #1090, but the sites-enabled copy does NOT.
As a result, nginx was rejecting agent event sync payloads (~1.7MB) with 413 despite the fix allegedly being deployed.
Root Cause
Nginx role copies the file rather than creating a symlink, so sites-available and sites-enabled can diverge.
Temporary Fix
Manually added client_max_body_size 10m; directly to /etc/nginx/sites-enabled/autobot-slm and reloaded nginx (Feb 22).
Required Permanent Fix
- Ansible nginx role should either use symlinks or copy sites-available to sites-enabled atomically
- Verify both files match after any Ansible deployment
Discovered During
Severity
Medium — event sync was silently failing due to 413s
Activity
fix(ansible): replace non-symlink nginx sites-enabled file (#1122)
mrveiss commentedon Feb 22, 2026
Fix
PR #1125 adds three tasks to the
slm_managerAnsible role nginx section:sites-enabled/autobot-slmto check if it is a symlinkbecome: yes)This ensures Ansible's symlink task always succeeds even when a previous deployment left a standalone file at
sites-enabled/autobot-slm.Temporary manual fix applied Feb 22 (added
client_max_body_size 10m;directly to/etc/nginx/sites-enabled/autobot-slmon .19) has been in effect since then — agent event sync confirmed working.Closing once PR #1125 is merged.
Merge pull request #1126 from mrveiss/fix/1116-f541
Merge pull request #1125 from mrveiss/fix/1122-nginx-symlink