Skip to content
English
Manage and Create Tickets
  • There are no suggestions because the search field is empty.

File Uploads to Managed Wasabi S3 Fail Due to Invalid Endpoint and Missing Custom Bucket

Original Question or Issue:

File uploads to Team Folders configured with FileCloud Managed S3 storage were failing.

The customer observed two issues:

  1. Team Folders and subfolders could be created successfully, but files could not be uploaded to them.
  2. When an upload failed at the S3 storage backend, File Operations displayed the upload as successful, even though the file was not actually stored and the upload had failed.

The environment was using a newly configured Wasabi S3 bucket that had not previously been used with FileCloud.

Environment:

  • Product - FileCloud Server
  • Version - 23.262
  • Platform - Windows, Linux

Steps to Reproduce:

  • Configure Managed S3 Storage in FileCloud using Wasabi.
  • Specify a custom S3 bucket name that has not yet been created in Wasabi.
  • Configure the S3 endpoint without the URL scheme, for example:
    s3.us-central-1.wasabisys.com
  • Create a Team Folder configured to use the Managed S3 storage.
  • Create folders or subfolders within the Team Folder.
  • Attempt to upload a file.
  • Observe that the folder structure can be created, but the actual file upload to the S3 backend fails.
  • In some cases, File Operations may report the upload as successful even though the backend storage operation failed.

Error or Log Message:

The FileCloud server logs showed:

Custom endpoint 's3.us-central-1.wasabisys.com' was not a valid URI

Followed by errors similar to:

addFile: Error saving file to storage backend

The logs also showed that the upload request could initially receive an HTTP 200 response before the subsequent S3 storage operation failed:

Enabling optimized file uploads with pipelining, sending response and continuing. Sending response for upload with: httpCode=200

Defect or Enhancement Number:

 

Cause:

 There were two configuration issues affecting the Managed S3 storage: 

1. Invalid S3 endpoint format

The S3 endpoint was configured as:

s3.us-central-1.wasabisys.com

The endpoint was not recognized as a valid URI because the URL scheme was missing.

2. Custom S3 bucket had not been created

After correcting the endpoint URL, uploads still did not work because the custom bucket specified in the FileCloud configuration had not yet been created in Wasabi.

When using a specific custom bucket name, the required bucket needed to exist in Wasabi before it could be used by the FileCloud Managed S3 configuration.

The ability to create Team Folders and subfolders did not confirm that S3 file storage was functioning. FileCloud can maintain folder structure and associated metadata separately, while uploading actual file content requires a successful connection to and write operation against the configured S3 backend.

Resolution or Workaround:

  1. Update the S3 Endpoint URL from:
s3.us-central-1.wasabisys.com

to the fully qualified endpoint:

https://s3.us-central-1.wasabisys.com
  1. If specifying a custom bucket name, ensure that the bucket has been created in Wasabi in the appropriate region before configuring it in FileCloud.
  2. Return to the FileCloud Managed S3 configuration and click Save S3 Settings.
  3. Test uploading a file to a Team Folder using the Managed S3 storage.

After correcting the endpoint URL and ensuring that the specified bucket existed in Wasabi, the customer confirmed that files were uploading successfully.

Notes: