After recent update, I get the following error. and some of my users claim they cant update whitelisted files. Aws::S3::Errors::NotImplemented (A header you provided implies functionality that is not implemented) /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/aws-sdk-core-3.48.6/lib/seahorse/clie…

Is your S3 bucket on Amazon S3?

No. I’m using my own minio server.

Then the error is fairly self explanatory. Discourse is using an S3 feature that minio doesn’t implement.

yes. but what is it? and how can I disable/fix it?

Your best bet is to look at recent commits having to do with s3

As far as I see the newest change that I didnt have is secure upload feature that I have it turned off in my forum. :confused:

any suggestions? more ppl are reporting this issue.

If I upload a picture, it doesnt let me to publish the post by throwing internal server error. However i can cut the uploaded picture url, publish the post, edit post and add that url, and publish it again.

Please give us the full backtrace of the error.

here it is : /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/aws-sdk-core-3.48.6/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call' /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/aws-sdk-s3-1.36.1/lib/aws-sdk-s3/plugins/sse_cpk.rb:22:in `call' /var/www/discourse/vendor/bundle/ruby…

Minio : Un en-tête fourni implique une fonctionnalité S3 qui n'est pas implémentée

Soutien

Falco (Falco) Avril 5, 2021, 1:35 20

Cela fonctionne et nous avons un guide à ce sujet sur Utilisation du stockage objet pour les téléversements (S3 et clones)

Sujet		Réponses	Vues
Can not edit topics with picture with S3 backend Bug	11	1191	Juillet 12, 2021
Why run UpdatePostUploadsSecureStatus even when secure uploads is disabled? Support s3	5	519	Février 20, 2023
Secure Uploads Announcements secure-uploads	46	17291	Juillet 24, 2025
Set up file and image uploads to S3 Self-Hosting configuring , how-to	35	120274	Octobre 25, 2025
S3 migrations from/to minio problems Bug	46	5090	Janvier 10, 2020

Minio : Un en-tête fourni implique une fonctionnalité S3 qui n'est pas implémentée

Sujets connexes