Public sharing setup

Hey. I can't seem to figure out how to setup public link sharing. I have looked into the documentation (https://help.ente.io/self-hosting/faq/sharing) but im still confused. Now when i share the public link it correctly generates with "albums.my-domain.com" but shows login screen just like "foto.my-domain.com". Here im sending part of my compose.yaml file and museum.yaml file (ente runs behind nginx reverse proxy so i added where it is rerouted). How do i set it up correctly? If someone could send an example it would be much appreciated!
Album sharing | Ente Help
Getting album sharing to work using an self-hosted Ente
No description
No description
9 Replies
Ducky
Ducky5mo ago
Remember to use /solved to mark your thread as solved once your question is answered.
Keerthana
Keerthana5mo ago
Hey there, you don't have to use 2 services, one is enough and configuring web service alone with correct albums origin should do the trick
RJ SKULL
RJ SKULL4mo ago
I'm having the same issue, the albums port is redirecting to a login page.
RJ SKULL
RJ SKULL4mo ago
This help article seems to state differently https://help.ente.io/self-hosting/faq/sharing "You'll need to run two instances of the web app, one is regular web app, but another one is the same code but running on a different origin", but the configs make it seem that 1 instance is able to do both.
Album sharing | Ente Help
Getting album sharing to work using an self-hosted Ente
SuperD9241
SuperD92414mo ago
That is the intent. It sounds as if you do have it working correctly but are expecting the wrong result. This port is open only to serve shared album links publicly. If you try to just visit the endpoint url, it will redirect you to the official Ente webpage. This is to send unintended public traffic away from your server. If you create a shared link within your logged in instance, it will generate a working public url using that endpoint.
RJ SKULL
RJ SKULL4mo ago
Yes, I mean generated links redirect to the login page of my server. Sorry for leaving that part out.
SuperD9241
SuperD92414mo ago
Does your compose file look like the image above? If so, please uncomment lines 39 & 42.
Keerthana
Keerthana4mo ago
Sorry about this, this is a deprecated article which will be removed in the new self-hosting docs revision, which you can expect to be released by the end of week. You can just expose the port 3002 in web service and it should work as expected, setting ENTE_ALBUMS_ENDPOINT alone is more than enough
Heather
Heather3mo ago
Having the same issue where the generated public links prompt for a login. I am running it as a single service
web:
image: ghcr.io/ente-io/web
ports:
- 3000:3000 # Photos web app
- 3002:3002 # Public Albums
- 3004:3004 # Cast
environment:
ENTE_API_ORIGIN: https://ente.mydomain.xyz
ENTE_ALBUMS_ORIGIN: https://ente-app.mydomain.xyz/albums
web:
image: ghcr.io/ente-io/web
ports:
- 3000:3000 # Photos web app
- 3002:3002 # Public Albums
- 3004:3004 # Cast
environment:
ENTE_API_ORIGIN: https://ente.mydomain.xyz
ENTE_ALBUMS_ORIGIN: https://ente-app.mydomain.xyz/albums
The links generate properly and have the expected format https://ente-app.mydomain.xyz/albums?t=<key>#<album-link> but when navigated to it prompts for a login which is unexpected. Edit: pulled the latest docker image and now it's working. Am running ghcr.io/ente-io/web@sha256:89de130fb9630a25d8d928dce747fc4e2a505af18cecb35089bc8d3300fc552c

Did you find this page helpful?