Problem:
Since the current NS8 Nextcloud module ships Nextcloud 33.0.1, it is impossible to share files or folders with internal users via the web interface. The “Save share” button does not respond – no request is sent to the server. This affects all browsers (tested: Firefox and Edge on the same system).
This is a confirmed upstream bug, reported on GitHub:
Fix status:
The bug is fixed in Nextcloud 33.0.3 (released April 30, 2026).
Request:
Please update the NS8 Nextcloud module to ship Nextcloud 33.0.3 or later. File sharing is a core function and currently completely broken for all users on NS8 instances running module version 1.7.0.
at least not intentionally - I corrected some errors, e.g. repair mysql db index and fixed other stuff such as languange / locale settings. I do have a track of entered commands and will review, but from here I am pretty shure that I did not update via command line and to the best of my knowledge I did not touch the button in the web interface manually. Howerver I did all clean up on two independend clusters (domain1.com and mydomain.world). I just counterchecked: I found the error on domain1.com but not on mydomain.world - which strongly indicates your supposition.
The bot and I checked yesterdays chat on resolving this and other issues on nextcloud
No – in this chat, no Nextcloud core update was triggered via Podman. We exclusively ran occ commands (app activations/deactivations, maintenance:repair, db:add-missing-indices, notify_push installation), but no podman pull or image update. The Nextcloud core remains unchanged at 33.0.1.
occ cannot trigger a Nextcloud core update. It operates only within the running container and has no access to the container image layer. A core update in NS8 would require either a module update through the NS8 Software Center (which replaces the container image) or a manual podman pull followed by a container restart.
by change, which version of nextcloud was included in module 1.7.0? I found:
nextcloud-app:1.7.0 running since 28.05.2026.
first entry for 3.0.1.2: 01.06.2026 19:17:19 local time -
No hit for version":"32..
but here is my diary:
I wanted to leave office around 17:30, but a collegue asked me to provide some access. We configured passbolt and nextcloud for which I had to create a user. Than I showed him how Nextcloud works, but at that point we were not able to share a file. I was initially thinking of a browser problem, but I did not wanted to step into details - I was annoyed that I could not show nextcloud features, but it was late, so I pushed im out (gladly he has not noticed the problem) and startet to work on the issue until close to 20:00 when I finaly decided to leave and let the issue be an issue.
The chat with Claude / chatgpt did not resolve any command line updates for nextcloud in that timeframe or before. Is it somehow possible that either the disabling / re enabling of some modules including file sharing, might have triggered something?
ahh, you mean it was intended not to update to 1.7.0 because it had the broken 33.0.1? Than it is clear, because I did that update note knowing about the bug
Sorry, I would not consider this as solved nor as a support request for a simple reason a buggy modul version was released to the public and some - maybe just me - might have installed it. …
no need to excuse, you are doing well a I simply captured that version in the morning - bad luck. but maybe I am wrong - someone closed my post as solved and (from my notification) it was moved from bug to support. I just complained about that. Nexcloud is perfect and I am happy you shared this information - Markus provided some details on how downgrade, but I I am still unsure do do so if an update is foreseeable in the near future. Thats why I wanted to keep this open as a bug
