Unable to upload

[trev0r-STA]

Hi all
Experienced with linux and programming in general, but totally new to docker and it's not easy, I know why I've never wanted to use it 😁
I can't upload, I'm running the Quickstart script with some little modifications. I believe I've configured the CORS, but now... I don't know where to search.
Firewall is open, reverse proxy is set...

compose.yaml
`services:
museum:
image: ghcr.io/ente-io/server
ports:
- 8080:8080 # API
depends_on:
postgres:
condition: service_healthy
volumes:
- ./museum.yaml:/museum.yaml:ro
- ./data:/data:ro
healthcheck:
test: ["CMD", "wget", "--quiet", "--tries=1", "--spider", "http://localhost:8080/ping"]
interval: 60s
timeout: 5s
retries: 3
start_period: 120s

socat:
image: alpine/socat
network_mode: service:museum
depends_on: [museum]
command: "TCP-LISTEN:3200,fork,reuseaddr TCP:minio:3200"

web:
image: ghcr.io/ente-io/web
# Uncomment what you need to tweak.
ports:
- 3000:3000 # Photos web app
# - 3001:3001 # Accounts
- 3002:3002 # Public albums
# - 3003:3003 # Auth
# - 3004:3004 # Cast
# - 3005:3005 # Share
# - 3006:3006 # Embed
# - 3008:3008 # Paste
# Modify these values to your custom subdomains, if using any
environment:
ENTE_API_ORIGIN: http://localhost:8080
ENTE_ALBUMS_ORIGIN: http://localhost:3002
ENTE_PHOTOS_ORIGIN: http://localhost:3000

postgres:
image: postgres:15
environment:
POSTGRES_USER: pguser
POSTGRES_PASSWORD: db_pass
POSTGRES_DB: ente_db
healthcheck:
test: pg_isready -q -d ente_db -U pguser
start_period: 40s
start_interval: 1s
volumes:
- postgres-data:/var/lib/postgresql/data

minio:
image: minio/minio
ports:
- 3200:3200 # MinIO API
# Uncomment to enable MinIO Web UI
# - 3201:3201
environment:
MINIO_ROOT_USER: minio-user-XXXXX
MINIO_ROOT_PASSWORD: minio_pass
command: server /data --address ":3200" --console-address ":3201"
volumes:
- /home/data/ente:/data
post_start:
- command: |
sh -c '
#!/bin/sh

      while ! mc alias set h0 http://minio:3200 minio-user-XXXXX minio_pass 2>/dev/null
      do
        echo "Waiting for minio..."
        sleep 0.5
      done

      cd /data

      mc admin config set h0 api cors_allow_origin="*"
      mc mb -p b2-eu-cen
      mc mb -p wasabi-eu-central-2-v3
      mc mb -p scw-eu-fr-v3
      '

volumes:
postgres-data:
minio-data:
`

museum.yaml
`db:
host: postgres
port: 5432
name: ente_db
user: pguser
password: db_pass

s3:
# Top-level configuration for buckets, you can override by specifying these configuration in the desired bucket.
# Set this to false if using external object storage bucket or bucket with SSL
are_local_buckets: true
# Set this to false if using subdomain-style URL. This is set to true for ensuring compatibility with MinIO when SSL is enabled.
use_path_style_urls: true
b2-eu-cen:
# Uncomment the below configuration to override the top-level configuration
# are_local_buckets: true
# use_path_style_urls: true
key: minio-user-XXXXX
secret: minio_pass
endpoint: http://minio:3200
region: eu-central-2
bucket: b2-eu-cen
wasabi-eu-central-2-v3:
# are_local_buckets: true
# use_path_style_urls: true
key: minio-user-XXXXX
secret: minio_pass
endpoint: http://minio:3200
region: eu-central-2
bucket: wasabi-eu-central-2-v3
compliance: false
scw-eu-fr-v3:
# are_local_buckets: true
# use_path_style_urls: true
key: minio-user-XXXXX
secret: minio_pass
endpoint: http://minio:3200
region: eu-central-2
bucket: scw-eu-fr-v3

apps:
# If you're running a self hosted instance and wish to serve public links,
# set this to the URL where your albums web app is running.
public-albums: http://localhost:3002
cast: http://localhost:3004
# Public locker (share) app
public-locker: http://localhost:3005
# Public paste app
public-paste: http://localhost:3008
# Embed app for embedded album sharing
embed-albums: http://localhost:3006
# Set this to the URL where your accounts web app is running, primarily used for
# passkey based 2FA.
accounts: http://localhost:3001

key:
encryption: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
hash: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

jwt:
secret: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

internal:
admin: xxxxxxxxx`

[PedroC88]

You should post this in the “issues” section since discussions are more for feature suggestions and feedback, having said that, check your docker logs (one container at a time) and post any errors (on the issues section).

[trev0r-STA]

Oh sorry, for posting in the wrong section. I'll try this even if I don't know how to look for logs container per container.
But I'll find.
Thanks

[rrp872]

Hi @trev0r-STA ,
maybe in museum.yaml your endpoints are wrong?
In my self-hosting server, I needed to replace localhost with my server's IP (or domain).

[trev0r-STA]

finally used the quickstart script and it work like a charm. Don't really know what I've messed with the config

[PedroC88]

Note that the quick start script is not the best permanent solution, it’s just there to get you started. IMHO one of the biggest issues is Minio which is discontinued. You should provide a different S3 storage through the composer (and generate new JWT keys and Postgres’s password). It’s all there in the documentation. Pedro Sánchez Gracias por su Tiempo

…

On Wed, May 13, 2026 at 14:35 trev0r-STA ***@***.***> wrote: finally used the quickstart script and it work like a charm. Don't really know what I've messed with the config — Reply to this email directly, view it on GitHub <#10295 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUSAX25Y54LPNZHL6HIRGT42S6ABAVCNFSM6AAAAACYRS5HW6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOJQHA3DSMQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[PedroC88]

Disclaimer: I'm just a community member like you guys (Ente user) and not part of the Ente team, I'm also new to Ente and I'm figuring things out as I go, so take my advice with a grain of salt and feel free to ignore any advice that you think is "stupid".

Here's my recommended advice, and at the bottom I added some debugging instructions, without logs we can't help you determine the issue, so if you're still having problems after building a new environment with these instructions, give us the logs and the container with the issue.

1. Documentation: Here's the link for self-hosting
   • I recommend you follow the docs and provision an instance with minio first, and only provide a custom s3 storage (by removing the minio and socat containers from the composer file -and the minio volume-) after it's up and running
   • I also added a restart: unless-stopped instruction to each container so the services come back up after restarting the computer
   • Generate new JWT tokens (instructions are in the doc), and update the key section of the env file
   • The key and secret of the s3 section will be your minio user and secret (and would need to be updated when and if you provide your own S3 storage)
   • Be sure to also follow the post-deployment steps further down in the docs
2. Reverse Proxy: This isn't a requirement to run Ente, I would recommend you spin up a new instance WITHOUT a proxy in the middle and only add the proxy after it's up and running, especially if you'll provide a custom S3 storage. Be sure to use the IP of the service when referencing it, or pushing images will fail is you use friendly names.
3. Object Storage: To upload media to the storage account the client connects to the API with the upload request and API responds with the URL of the storage, the client then pushes directly to the storage and then communicates back to the API for validation, which is why I recommend you don't use the reverse proxy from the get go.

Essentially, Ente is a very complex system and while setup is a bit straight forward, having so many moving parts increases the risk of the system failing to boot, adding more complexity (like custom storage or proxy servers) until the basics are cleared will make you go insane if things go bad.

After you run your compose file (I also recommend basing your composer on the example from source code as noted in the instructions and not on the quick-start) you should test each container's logs to see if there are errors being reported. See docker logs for instructions now how to get logs for containers.

[trev0r-STA]

@PedroC88
I've finally install ente with the documentation. And seems to wotk fine, I'm facing a last problem (I hope), how can I move the database from the quick start container to the definitive one. I've made a dump of the db but can't inject it in the new one. Database already exist and I can't delete it, because it's in use.... Some idea ?

[PedroC88]

Do you really need that data? I personally just deleted everything over and over until I got it working on a clean install.

I’ve never done it so these options are just guesses:

• Export a backup using docker copy, copy it back to the final container and do a database restore (I don’t know how Postgres manages users so I can’t certify this works)
• Point your new Ente instance to the old Postgres via the docker compose file and env files.

In either case, since the database and storage (minio) have to be in sync, I don’t think it will work to restore a database with data with an empty storage.

If you can provide more details on why you want to do this, I may be able to give you other alternatives.

[trev0r-STA]

My connection is very bad, so I've upload 22Go of picture on the server (which take me a looooong time) and I want to avoid to resend them. I've keep the credentials for database connection, minio connection, so data are on the server and I just want to add those data to the database. I've create a dump of the quick-ente database with the pg_dump command, but I can't restore it in the new container
I've tried a lot of different options with pg_restore, but nothing:
I've had errors, and actually with:
pg_restore -U pguser -f "/var/lib/postgresql/data/ente_db_backup.dump"
nothing happened, no error, just waiting, need to Ctrl+C to finish the command (and I've wait a lot of time before to Ctrl+C)

[PedroC88]

Yeah, in that case then go with those options (assuming you’re self hosting remotely, because if you’re self hosting at home, you can use the internal ip and then 22GB should go very quickly).