Self hosted public link has wrong domain

I originally set up my self hosted instance with a .tech domain and later changed it to .au I have updated everything in museum and compose yamls, any its all working great, except for the public sharing links. For some reason, they still have the .tech domain. If I manually change the domain in the generated URL, for instance: https://ente.DOMAIN.tech/?t=NciYfWNb#5vEnGHGHGSGHSTNvr1ZfJDgrLzLCs6HBU3e65wAEi to https://entepublic.DOMAIN.au/?t=NciYfWNb#5vEnGHGHGSGHSTNvr1ZfJDgrLzLCs6HBU3e65wAEi then it will work. My compose has: environment: ENTE_API_ORIGIN: https://enteapi.DOMAIN.au ENTE_ALBUMS_ORIGIN: https://entepublic.DOMIAN.au Why would it still be remembering in this one thing?
13 Replies
Ducky
Ducky3w ago
To update the domain for public sharing links in your self-hosted instance, ensure that the ENTE_API_ORIGIN and ENTE_ALBUMS_ORIGIN environment variables in your docker-compose.yaml file are correctly set to your new domain. You can configure these variables in your docker-compose.yaml file, as shown in this example:
environment:
ENTE_API_ORIGIN: https://enteapi.DOMAIN.au
ENTE_ALBUMS_ORIGIN: https://entepublic.DOMIAN.au
environment:
ENTE_API_ORIGIN: https://enteapi.DOMAIN.au
ENTE_ALBUMS_ORIGIN: https://entepublic.DOMIAN.au
See the docker-compose.yaml example at https://ente.io/help/self-hosting/guides/windows#docker-composeyaml for more details. -# If your issue is resolved, feel free to use the /solved command to close this thread. If you'd like to ask me another question use /docsearch
Self-hosting Ente on Windows | Ente Help
A community guide with a Windows specific workflow for running the self-hosted version on Ente
Gr0p3r
Gr0p3rOP2w ago
Yeah, that doesn't help. You just repeated what I already said I am doing.
Ducky
Ducky2w ago
Quack :lilducky:
Brogio
Brogio2w ago
Note: I don't work on Ente's codebase. But wouldn't those URL's be stored in the database that still has .tech
Gr0p3r
Gr0p3rOP2w ago
I guess that would make sense if the URLs were generated before changing the domain. But these are URLs that have been generated after everything was changed over for weeks.
Brogio
Brogio2w ago
In that case the only reason I could logically think of is that somewhere in a config is still .tech
Gr0p3r
Gr0p3rOP2w ago
thinking about this some more, and actually I don think it would have the domain saved in DB. Because if I just change the domain in the generated URL, it works. Therefore it must just be using the sting at the end for it to work. Anyway, I cant see anywhere that my config is wrong. Ive scoured it for .tech domain and its nowhere to be seen. Heres the apps section of Museum.yaml
No description
Servers@Home
Servers@Home2w ago
hate to hijack this thread but just curious since i am having a similar problem. i click the button to generate a link to an album and then click the "copy link" button but it doesnt copy anything. i cannot see the link (if its being created at all). how did you get this working on your end @Gr0p3r?
Gr0p3r
Gr0p3rOP2w ago
Sorry, can't remember. I've been dicking around with too many things. But I know I did have the same thing, it would not generate links. I think maybe it was adding the "public-album: " to apps in museum.yaml. Or it could have been in compose. At the time, I wasn't trying to fix that issue, I was still trying to get my reverse proxy working. But somethine in all of it made it work, but now it's just got the wrong damn url lol.
Servers@Home
Servers@Home2w ago
im curious what does your docker compose look like? i cant understand why mine isnt working. i have an entry for public-albums in my museum.yaml
Josh
Josh2w ago
iirc ente web must be seperately configured via. environment variables. Have you checked those ? I might be wrong for your set-up though because I'm not using docker-compose ALBUMS_ORIGIN is possibly the var
Gr0p3r
Gr0p3rOP2w ago
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", "curl", "--fail", "http://192.168.11.4:8080/ping"] interval: 60s timeout: 5s retries: 3 start_period: 5s # Resolve "192.168.11.4:3200" in the museum container to the minio container. 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 # Modify these values to your custom subdomains, if using any environment: #ENTE_API_ORIGIN: http://192.168.11.4:8080
ENTE_API_ORIGIN: https://enteapi.#######.au #ENTE_ALBUMS_ORIGIN: http://192.168.11.4:3000 ENTE_ALBUMS_ORIGIN: https://ente.#######.au NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT: https://entepublic.#######.au postgres: image: postgres:15 environment: POSTGRES_USER: pguser POSTGRES_PASSWORD: ####### 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 ports: - "5432:5432" minio: image: minio/minio ports: - 3200:3200 # MinIO API # Uncomment to enable MinIO Web UI
- 3201:3201 environment: MINIO_ROOT_USER: minio-user-####### MINIO_ROOT_PASSWORD: ####### command: server /data --address ":3200" --console-address ":3201" volumes: - minio-data:/data post_start: - command: | sh -c ' #!/bin/sh while ! mc alias set h0 http://192.168.11.4:3200 minio-user-####### ####### do echo "Waiting for minio..." sleep 0.5 done # cd /data # 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: Yes, thats declared in the docker compose file as ENTE_ALBUMS_ORIGIN: https://ente./#######.au

Did you find this page helpful?