Hello,
we hit the same failure on one of our instances (package 1.1.4 / DocumentServer 9.3.8.37, Nextcloud 35.0.3, connector 11.0.6) and your analysis matched what we saw. We also recomputed the secure_link signature of a rejected URL and it was valid.
Two additions that may be useful:
- Adding
www-datato thedsgroup was not possible for us: the container root file system is read-only (usermod→ "cannot lock /etc/passwd"). Only/tmp,/runand/app/dataare writable. - What helped us instead was an ACL entry
u:www-data:r-x, as default ACL on/tmpand on.../App_Data/cache/files/data, plus once recursively for the files already there. New files created in/tmppick the entry up automatically, and since it is stored with the file itself it also survived the rename into the cache for us. Owner and mode of the files stay unchanged. (setfaclwas not installed in our image, so we set the ACL attribute directly.)
After that /cache/files/... returned 200 instead of 403 for us, occ eurooffice:documentserver --check reports "successfully connected", and opening and editing docx and xlsx works again. Because /tmp and /app/data are persistent volumes, we expect it to survive restarts as well. We have not been through an app update with it yet, so we kept it as a stopgap and kept the connector's cron check as our alarm, which mails the admins as soon as the check fails again. Whoever prefers to stay on an unchanged package can also restore the pre-update backup instead, but then auto updates for the app should stay off.

