Skip to content

[bug] Spaces in custom integration filenames cause an extraction error #842

Open

Description

@kennymc-c

Is there an existing issue for this?

  • I have searched the existing issues

Description

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

  1. Add a space to the filename of a custom integration archive
  2. Upload it to the remote
  3. 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

  1. self-assigned this
    on Nov 4, 2026
  2. moved this from Reported to In Progress in Bug reportson Nov 4, 2026
  3. moved this from In Progress to Done in Bug reportson Nov 5, 2026
  4. zehnm commented on Nov 5, 2026

    @zehnm

    Fix should be included in next release.

  5. zehnm commented on Nov 6, 2026

    @zehnm

    Tested on the Remote. Fix is included in next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcoreCore related issue

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions