Issues observed with Frappe S3 Attachment app on rushabh-test.frappe.cloud

Pallavi01 · September 3, 2025, 2:04pm

Hello Team,

I have configured the Frappe S3 Attachment v0.0.1 (HEAD) app on the site rushabh-test.frappe.cloud with all the required details, but I am facing some issues:

While uploading a file, it doesn’t get uploaded as public unless we explicitly select the private option. Even after setting default to all public, it doesn’t work.
The app provides an option to migrate existing files to S3, but when I click it, I get a failed error.
If the configuration was incorrect, then when adding a file through the UI with private selected, it should not go to S3 — but it does. How is this possible?
Similarly, when a file is created from the backend, it is correctly stored in S3.

So, why are the existing files not migrating, and why is the public option not working? Could you please check and let us know what might be missing or wrong in the setup?

I have also attached the respective screenshots for your reference.

peterg · September 3, 2025, 2:22pm

Your best bet would be to reach out to the owners of this app on GitHub. They may or may not be watching posts here. The repo hasn’t seen much activity over the past several years, so it may be significantly outdated.

tmatteson · September 3, 2025, 4:41pm

We offer an updated alternative to Zerodha’s app: GitHub - agritheory/cloud_storage: S3 protocol storage for Frappe Applications - compatible with S3, Backblaze and DO Spaces

Sandeep_Kakde · September 3, 2025, 5:28pm

It looks like ACLs is disabled in the Object Ownership. If yes then you can’t upload the public files. You’ll have to update the Object Ownership settings for this.
If you don’t want to update the Ownership settings, then you have to remove the following line from the code. you can take the fork and remove this line.

github.com/zerodha/frappe-attachments-s3

frappe_s3_attachment/controller.py

eaa24ca26


      
                              "ContentType": content_type,
                              "file_name": file_name
                          }
                      }
                  )
              else:
                  self.S3_CLIENT.upload_file(
                      file_path, self.BUCKET, key,
                      ExtraArgs={
                          "ContentType": content_type,
                          "ACL": 'public-read',
                          "Metadata": {
                              "ContentType": content_type,
          
                          }
                      }
                  )
          
          except boto3.exceptions.S3UploadFailedError:
              frappe.throw(frappe._("File Upload Failed. Please try again."))
          return key

Pallavi01 · September 4, 2025, 9:27am

Hello Sandeep ,
Thanks for your reply .
But what about it is giving the error while migrating existing files .
Can you please help me with the same .

Sandeep_Kakde · September 4, 2025, 10:15am

Can you check the browser console and network console for more details on the error. Also paste the errors here.

Pallavi01 · September 4, 2025, 11:00am

Sandeep_Kakde · September 4, 2025, 3:03pm

This doesn’t show any error, can you click on the Migrate Existing Files and then check the network & browser console.

Pallavi01 · September 8, 2025, 10:43am

Hello Sandeep,

it shows only below output while checking after clicking on migrate existing files

Sandeep_Kakde · September 8, 2025, 5:54pm

HTTP Status is 417 can you click on it and check the response from the server.

Pallavi01 · September 9, 2025, 10:02am

Here is the output

Sandeep_Kakde · September 9, 2025, 1:48pm

Click on the response tab and share the screenshot.