Repository navigation
[Bug]: uploading a folder into a folder, wich name starts with # fails using any browser #62716
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
Errors when uploding folders with files into a folde whose name starts with #
i.E. #test, #Infos, ...
Steps to reproduce
- use a browser fpr uploading a folder from ypur local data
- create a new folder at server named i.e. #testupload (name has to start with #) and go into
- use ui (new , ulpload folder ) or use mouse to drop a local folder
- Errors: the folder does not exist any more
-> files were uploaded , folders not
Expected behavior
Folder Upload into any folder at server as it has been working before 33
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
using Nextcloud 33.0.6 hostet by Hetzner as StorageShare
Activity
brlin-tw commentedon Oct 22, 2026
Seems to be a regression of #59294, see: #59294 (comment)
Overdrive4954 commentedon Oct 27, 2026
Still reproducible on 34.0.5 (Debian 13, nginx 1.26.3, PHP 8.4.27), with both drag-and-drop and New → Upload folder, in Chrome 156 (Linux) and Chrome 148 (macOS).
It also happens when the
#is in any parent of the current folder, not only the current folder's own name (e.g.#test/Sub folder).The access log shows the uploader computes the new folder's path truncated at the
#. With Upload folder, it checks the correct path, then sendsMKCOLto the user's root:With drag-and-drop, it checks the truncated path, finds the root exists, and never sends
MKCOL:The file
PUTs and the destinationPROPFINDencode the#correctly as%23; only the path used for creating the new folder loses everything from the#onward. Uploading a folder whose own name contains#(from a parent without#) works correctly, and folder uploads into subfolders without#(e.g.Documents) also work, so the general fix for #58454 / #59672 is in place on this instance. This looks like the#case surviving that fix.Workarounds for affected users: create the destination folder manually and upload the files into it (single-file uploads are unaffected), or rename the parent folder to remove the
#.