S3 File Upload Failing with Infomaniak Cloud Storage - ENOENT Error on File Deletion

[Teddydesta]

�� Bug Report

Environment

• LibreChat Version: v0.7.8
• Cloud Platform: Infomaniak Cloud Storage (S3-compatible)
• Deployment: Kubernetes
• Backend: Node.js

Issue Description

File upload functionality is failing with S3 upload errors and subsequent ENOENT file deletion errors. The issue occurs when users attempt to upload images/files through the LibreChat interface.

Error Logs

2025-08-15T07:41:18.748Z error: [saveBufferToS3] Error uploading buffer to S3:
2025-08-15T07:41:18.748Z error: [uploadImageToS3] Error uploading image to S3:
2025-08-15T07:41:18.749Z error: [/files/images] Error processing file:
2025-08-15T07:41:18.750Z error: [/files/images] Error deleting file: ENOENT: no such file or directory, unlink '/app/client/public/images/689db22e002485246d608d11/Screenshot_2025-07-... [truncated]
2025-08-15T07:41:18.751Z debug: [/files/images] Temp. image upload file deleted

Configuration Details

• S3 Endpoint: https://s3.pub1.infomaniak.cloud
• File Strategy: s3
• Storage Backend: Infomaniak Cloud Storage (S3-compatible)

Steps to Reproduce

1. Deploy LibreChat with Infomaniak S3 backend
2. Attempt to upload an image/file through the chat interface
3. Observe S3 upload failure followed by ENOENT error

Expected Behavior

• Files should upload successfully to Infomaniak S3 storage
• No ENOENT errors should occur during file processing

Actual Behavior

• S3 upload fails with error
• System attempts to delete temporary file that doesn't exist
• ENOENT error occurs during cleanup process

Additional Information

• The issue appears to be specific to Infomaniak S3-compatible storage
• File upload functionality works with other S3 providers
• Error occurs in the file processing pipeline after S3 upload failure

Environment Variables

AWS_REGION=us-east-1
AWS_BUCKET_NAME=librechat
AWS_ENDPOINT_URL=https://s3.pub1.infomaniak.cloud

LibreChat Configuration

fileConfig:
  serverFileSizeLimit: 100 # MB
fileStrategy: s3

Questions for Investigation

1. Is there specific handling needed for Infomaniak S3-compatible storage?
2. Should the file deletion logic be more robust to handle missing temporary files?
3. Are there any known compatibility issues with Infomaniak's S3 implementation?

Priority

High- File upload is a core functionality that affects user experience

Labels

• bug
• file-upload
• s3
• infomaniak
• v0.7.8

[danny-avila]

Moved to troubleshooting since only S3 is officially supported, not all S3-like or S3-compatibile APIs are accounted for.

[Teddydesta]

Thanks for the clarification. We're using OpenStack Object Storage (S3-compatible) with LibreChat. Has anyone successfully used LibreChat with S3-compatible providers like OpenStack, MinIO, etc.?
Our config:

AWS_ENDPOINT_URL: "https://s3.pub1.infomaniak.cloud"
AWS_S3_FORCE_PATH_STYLE: "true"

Looking for community experience or workarounds for S3-compatible APIs.

[jangxx]

I had exactly the same issue with Hetzners S3 service today. Checking the log file revealed that the S3 server was returning a 403 error because I had switched the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.

Maybe you made the same mistake? And if you didn't, I would definitely suggest to check the log file for more information (not sure if you need to set DEBUG_LOGGING to true, but I had it set FWIW)