You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Spaces in custom integration filenames cause an extraction error #842
If the filename of a custom integration archive file contains a space, this causes an error when extracting the archive on the remote (see error message from the core log below).
In the past, some users have reported that integrations couldn't be uploaded, while others had no problems with it. The browser was often suspected of having already extracted the archive; however, when the same file is downloaded multiple times in Windows, for example, a “ (n)” is appended to the filename for each copy, and the leading space in the filename triggers this exact error.
How to Reproduce
Add a space to the filename of a custom integration archive
Upload it to the remote
Remove the space from the filename and upload it again
Expected behavior
The upload/extraction shoulnd't fail
System version
2.11.0
What part of the system affected by the problem?
Core
Additional context
Excerpt from the core service log:
2026-10-30 15:50:23.373012 +00:00 core WARN Error encountered while processing the incoming HTTP request: BadRequest("Could not extract archive")
2026-10-30 15:50:23.266814 +00:00 core ERROR Error extracting archive, status code: exit status: 1
Verify if installation archive exists
Verify if installation directory exists
Extracting custom integration archive...
Failed to start transient service unit: Source path with_spaces.tar.gz is not absolute.
2026-10-30 15:50:23.091034 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/extract-custom-intg.sh '/tmp/upload/custom_integration with_spaces.tar.gz' /tmp/upload/intg
Activity
zehnm commentedon Nov 5, 2026
Fix should be included in next release.
zehnm commentedon Nov 6, 2026
Tested on the Remote. Fix is included in next release.