This commit is contained in:
mngshm
2025-04-30 19:13:14 +05:30
parent 7735d938a5
commit e939b06339
3 changed files with 7 additions and 7 deletions

View File

@@ -269,15 +269,15 @@ export const sidebar = [
link: "/self-hosting/guides/admin",
},
{
text: "Configure CLI for your instance",
text: "Configuring CLI for your instance",
link: "/self-hosting/guides/selfhost-cli",
},
{
text: "Hosting Ente from source",
text: "Running Ente from source",
link: "/self-hosting/guides/from-source",
},
{
text: "Hosting Ente without Docker",
text: "Running Ente without Docker",
link: "/self-hosting/guides/standalone-ente",
},
],

View File

@@ -258,4 +258,4 @@ Some other users have also shared their setups.
- [Building custom images from source (Linux)](https://github.com/ente-io/ente/discussions/3778)
- [Troubleshooting Bucket CORS](/self-hosting/troubleshooting/bucket-cors)
- [Troubleshooting Bucket CORS](/self-hosting/troubleshooting/bucket-cors)

View File

@@ -3,13 +3,13 @@ title: Uploads
description: Fixing upload errors when trying to self host Ente
---
# FAQ's regarding S3
# 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
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.
@@ -51,4 +51,4 @@ This could be because
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.