docs(pfi-tacticalrmm): rmm-mesh nginx upload limit raised to 4G (was the 1 MB default)

This commit is contained in:
vh
2026-10-02 17:08:21 -07:00
parent 5c0d5f0a73
commit 56c372dd6f
+4
View File
@@ -52,6 +52,10 @@ Monitors and manages endpoints, pushes patches, runs scripts, etc.
`node node_modules/meshcentral --createaccount lkraven --hashpass <salt,hash>` + `--adminaccount lkraven` while `node node_modules/meshcentral --createaccount lkraven --hashpass <salt,hash>` + `--adminaccount lkraven` while
the service was stopped (the CLI writes the DB directly). TacticalRMM's mesh sync only manages `name___N` the service was stopped (the CLI writes the DB directly). TacticalRMM's mesh sync only manages `name___N`
accounts, so it leaves this one alone. TRMM's own MeshCentral superuser is `fosxggiw`. ⚠ Not in 2FA yet. accounts, so it leaves this one alone. TRMM's own MeshCentral superuser is `fosxggiw`. ⚠ Not in 2FA yet.
- **Uploads ("My Files") need nginx's limit raised:** `/etc/nginx/sites-enabled/meshcentral.conf` had no
`client_max_body_size`, so nginx's 1 MB default 413'd every real upload. Since 2026-10-02:
`client_max_body_size 4G` + `proxy_request_buffering off` (backup `.bak-20261002-upload`). Site admins have no
MeshCentral quota. ⚠ Re-check after a TacticalRMM update or reinstall rewrites the nginx sites.
- CLI access: `meshctrl.js` on this host with Prime's login token, vaulted - CLI access: `meshctrl.js` on this host with Prime's login token, vaulted
`pfi-tacticalrmm/meshcentral-login-token` (one line: `username: ~t:… password: …`). Example: `pfi-tacticalrmm/meshcentral-login-token` (one line: `username: ~t:… password: …`). Example:
`sudo -n -u tactical node /meshcentral/node_modules/meshcentral/meshctrl.js listdevicegroups --url wss://rmm-mesh.phasefinal.com --loginuser <u> --loginpass <p>`. `sudo -n -u tactical node /meshcentral/node_modules/meshcentral/meshctrl.js listdevicegroups --url wss://rmm-mesh.phasefinal.com --loginuser <u> --loginpass <p>`.