4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1cc54959af	nextcloud: repair the account only on a 401, never reset the throttle (issue 1253, review 2) ... Resetting Nextcloud's brute-force record for the docker gateway cleared it for every client behind that address: someone guessing passwords could drive the throttle to 429 and have the module's poll wipe it. A throttle is no evidence the password is wrong, so a 429 is now backed off only, and the back-off outlasts the throttle. The account's existence is read from user:info's exit status, since user:list pages.	2026-10-25 16:57:46 +01:00
jschoubben	962bc359a7	nextcloud: repair only the module's own account, read its existence from the user list, no admin group (issue 1253, review 1) ... occ's user:info says 'user not found' on stdout with an empty stderr, so the error read as 'occ produced no output' and mesh-admin was never made on novox: occ now says stderr and stdout both, and existence is read from user:list. The repair could reset whatever account the user setting names, the operator's included, and the 'admin' fallback is a hand-made install's human administrator: only mesh-admin is repaired now, and it is the default. The shares poll needs no admin rights, so the account gets no group. After a repair the throttle of the caller's address is reset, and a failing repair reaches the back-off's one loud line with occ's message.	2026-10-25 16:54:51 +01:00
jschoubben	67b13c42d3	nextcloud: repair the account on a throttle too, since a throttle follows refusals (issue 1253) ... Right after the delivery the first answer may be Nextcloud's 429, not a 401; without a repair then the account would never be made and the back-off would wait out a throttle that cannot end.	2026-10-25 16:40:54 +01:00
jschoubben	4021724ca4	nextcloud: make the mesh's own account match its secret when Nextcloud refuses it, and back off a refusal that stays (issue 1253) ... The image creates NEXTCLOUD_ADMIN_USER only on a fresh install. novox's instance was installed before the mesh adopted it, so mesh-admin was never created there, and the shares poll asked Nextcloud every minute with a login that cannot pass: 401, then Nextcloud's brute-force throttle (429), which also held the backup before a delivery. On a refused login the client now adds the account through occ (admin group), or sets its password to the module's own secret, passing it by OC_PASS so it is on no argv, and asks once more. A refusal that stays is said once and the poll backs off from 5 minutes to an hour instead of nine lines of XML every minute. An empty setting no longer becomes an empty name.	2026-10-25 16:40:01 +01:00