From 860760784a33f278d3e316e4b4c0f9bd43ffd3e9 Mon Sep 17 00:00:00 2001 From: Manav Rathi Date: Mon, 26 May 2025 09:33:54 +0530 Subject: [PATCH] Update doc --- .../self-hosting/troubleshooting/uploads.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/docs/self-hosting/troubleshooting/uploads.md b/docs/docs/self-hosting/troubleshooting/uploads.md index 6bfef9f923..3dbc7454f4 100644 --- a/docs/docs/self-hosting/troubleshooting/uploads.md +++ b/docs/docs/self-hosting/troubleshooting/uploads.md @@ -3,14 +3,14 @@ title: Uploads description: Fixing upload errors when trying to self host Ente --- -# Troubleshooting upload failures +# Troubleshooting upload failures Here are some errors our community members frequently encountered with the context and potential fixes. Fundamentally in most situations, the problem is because of minor mistakes or -misconfiguration. Please make sure to reverse proxy museum and MinIO API -endpoint to a domain and check your S3 credentials and whole configuration +misconfiguration. Please make sure to reverse proxy museum and MinIO API +endpoint to a domain and check your S3 credentials and whole configuration file for any minor misconfigurations. It is also suggested that the user setups bucket CORS on MinIO or any external @@ -21,10 +21,10 @@ this](/self-hosting/troubleshooting/bucket-cors). S3 is an cloud storage protocol made by Amazon (specifically AWS). S3 is designed to store files and data as objects inside Buckets and it is mostly used for Online -Backups and storing different types of files. +Backups and storing different types of files. -Ente's Docker setup is shipped with [MinIO](https://min.io/) as its default S3 provider. -MinIO supports the Amazon S3 protocol and leverages your disk storage to +Ente's Docker setup is shipped with [MinIO](https://min.io/) as its default S3 provider. +MinIO supports the Amazon S3 protocol and leverages your disk storage to dump all the uploaded files as encrypted object blobs. ## 403 Forbidden @@ -40,15 +40,15 @@ This could be because 1. The bucket CORS rules do not allow museum to access these objects. For uploading files from the browser, you will need to set `allowedOrigins` to - `*`, and allow the `X-Auth-Token`, `X-Client-Package` headers configuration - too. [Here is an example of a working + `*`, and allow the `X-Auth-Token`, `X-Client-Package`, `X-Client-Version` + headers configuration too. [Here is an example of a working configuration](https://github.com/ente-io/ente/discussions/1764#discussioncomment-9478204). 2. The credentials are not being picked up (you might be setting the correct credentials, but not in the place where museum reads them from). -## Mismatch in file size +## Mismatch in file size The "Mismatch in file size" error mostly occurs in a situation where the client is re-uploading a file which is already in the bucket with a different file size. The reason for re-upload could be anything including network issue, -sudden killing of app before the upload is complete and etc. +sudden killing of app before the upload is complete and etc.