[Bug]: S3 Upload Failed - Malformed Access Key Id. Download Delete

[Cristy94]

Error Message and Logs

After updating to the latest version (beta452), the Coolify back-up to S3 fails with this error:

Warning: S3 upload failed: mc: <ERROR> Unable to initialize new alias from the provided credentials. Malformed Access Key Id.

If I go to S3 Storages, everything looks fine and the connection can be validated.

Steps to Reproduce

1. Go to Settings -> Backup
2. Have S3 Enabled
3. Try to run Backup now

Example Repository URL

No response

Coolify Version

v4.0.0-beta.452

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

Linear Issue: COOLGH-96

[mustafatoktas]

Hi team 👋

I’m experiencing the same issue on the same Coolify version.

Goal

Use Cloudflare R2 as S3-compatible storage for Coolify database backups.

What I configured

1. Created an R2 bucket in Cloudflare.
2. Created an API token / key with at least Object Read/Write permissions.
3. Added the storage in Coolify → S3 Storage:
   • Endpoint: https://<account_id>.r2.cloudflarestorage.com
   • Bucket: <bucket-name>
   • Access Key: <redacted>
   • Secret Key: <redacted>
   • Region: whatever the UI requires (R2 is regionless)
4. Validate Connection was successful.

What works

• Local backups are created correctly.
• I can see .dmp files under:
  • /var/www/html/storage/app/backups/coolify/coolify-db-hostdockerinternal/

What doesn’t work

• After scheduled/manual backup runs, no objects appear in R2.
• I couldn’t find a clear S3/R2-related error:
  • php artisan logs:scheduled --all --date=YYYY-MM-DD shows no logs for those days.
  • grep -iE 'backup|s3|aws|r2|bucket|PutObject|ListObjects' /var/www/html/storage/logs/laravel.log didn’t show anything useful.

Manual verification (to rule out R2 credentials)

Inside the Coolify container, using MinIO client:

• mc alias set ...
• mc cp <local-dump> r2/<bucket>/<file>.dmp

This works and the objects are visible in the R2 dashboard.

Why this looks like a Coolify-side issue

Since:

• connection validation succeeds,
• local dumps are produced,
• manual mc upload works with the same endpoint/keys,
• but Coolify doesn’t upload automatically and logs don’t show a clear S3 failure,

this seems like a bug in the S3 backup integration for this version.

[Divkix]

I am on version v4.0.0-beta.453 and am also facing this issue, not able to backup. I can validate the connection but there is no backup in my backblaze b2.

[mustafatoktas]

I have the same screenshot

[Divkix]

I have the same screenshot

I got to fix it by removing everything and then installing again, wasn't easy but it works now.

[mustafatoktas]

I wonder what caused the problem? What difference did uninstalling and reinstalling everything make? My Coolify has a lot of resources installed. Frankly, I don't want to back them all up and reinstall them from scratch, and I think this is definitely a bug. I hope the developers address this.

[FlyingThaCat]

had some issue too, im using backblaze, at first it work normally but currently it throwing this error

[andrasbacsai]

This will be fixed in the next version.

But until then, can you please check if there is a extra space in the key or secret maybe?

[FlyingThaCat]

This will be fixed in the next version.

But until then, can you please check if there is a extra space in the key or secret maybe?

For my setup it doesnt have any whitespace on key and secret but somehow on the docker calls it introduce the whitespace

[Musta-Pollo]

I can confirm. For me it also adds extra space before Access Key. If you I remove the space and save it, it always puts it back.