You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Ente is a service that provides a fully open source, end-to-end encrypted platform for you to store your data in the cloud without needing to trust the service provider. On top of this platform, we have built two apps so far: Ente Photos (an alternative to Apple and Google Photos) and Ente Auth (a 2FA alternative to the deprecated Authy).
Went over the install scripts and made a list of things that are pending in order to get a clean installation:
Backend's IP needs to be hardcoded via NEXT_PUBLIC_ENTE_ENDPOINT and NEXT_PUBLIC_ENTE_ALBUMS_ENDPOINT env variables. Currently we set them as http://localhost:8080 and http://localhost:3002 respectively. This wont work, since these URLs are used by the Frontend when accessed by a browser. They need to be the IP of the LXC containers or the public URL for the backend.
The frontend is built into html, which means if user changes the LXC's ip manually or via DHCP, they'll need to rebuild the frontend and move everything again to /var/www/ente/apps/* directory manually
We currently don't install ente cli as part of our install script, we should add it as it is helpful in upgrading the account's subscription to unlimited (as mentioned by @tremor021 )
Once the initial User account is created, we need to verify the email using the verification code generated. That cannot be completed unless we setup SMTP, or by digging through the backend (museum)'s logs.
Ente CLI does not support creating user accounts, which means we cannot automate creating a default admin account whatsoever.
Since we cannot have a default admin account, it means we cannot elevate the account to unlimited subscription automatically as well, user's intervention is needed
Ente Cli is basically an API wrapper for museum, and it relies on keyring to store/fetch secrets. We don't install keyring as part of our install script. Although there seems to be a way to bypass it by using an env variable (refer: CLI: Allow setting secrets path via env var ente/ente#2426) but storing secrets in a txt file for an application that boasts E2EE seems like a flaw than a solution. I haven't tested it out yet.
I feel, we can get Ente working quite easily, @MickLesk has done a lot of the hard work already, there are a few quirks which we cannot resolve unless Ente team improves the self-hosted user experience like allows admin user creation via ente-cli, or by creating a default admin on museum setup. Maybe even a seed-data SQL script would be helpful. Without which we cant ensure a smooth unattended installation experience (which i would prefer tbh)
FYI: made some progress in the script. will test and ensure everything works and then raise a PR.
Was travelling for a week, will work on the PR over this weekend.
@MickLesk Can you check the PR once? I'm facing a very weird issue where if I execute the script in default mode or advanced without verbose I am facing crashes randomly. Error message simply says:
"General error/ Operation not permitted"
If I install via Advanced settings and verbose mode, everything installs normally
I have attached screenshot in the PR (we can discuss the issue in the PR itself)
Installation fails. Seems like the mc client container tries to set the alias and perform operations before the minio server has fully started and is ready to accept connections?
Can't get past the 3rd step with community script , looked around couldn't find any clues.:
ente-setup
=== Ente First-Time Setup ===
Enter your account email: sissy@mail.com
Step 1/4: Register your account
Open the web UI: http://192.168.8.103:3000
Create an account with: sissy@mail.com
Make sure you click 'Don't have an account?' and complete the signup form.
Press ENTER after you submitted the signup form...
Step 2/4: Getting verification code from logs...
Your verification code: 415380
Enter this code in the web UI to complete registration.
Press ENTER after you verified the code in the web UI...
Step 3/4: Looking up user and whitelisting admin...
Warning: User 'sissy@mail.com' not found in database.
Make sure registration was completed successfully.
=== Setup incomplete ===
After completing registration, run ente-setup again.
root@ente:~#
verified and uploaded an image, but it says user not found in database... if i list all users in the database they are listed...
root@ente:~# su - postgres
Ente LXC Container - DEV Repository
WARNING: This is a DEVELOPMENT version (ProxmoxVED). Do NOT use in production!
OS: Debian GNU/Linux - Version: 13
Hostname: ente
IP Address: 192.168.8.103
Repository: https://github.com/community-scripts/ProxmoxVED
postgres@ente:~$ psql -d ente_db
ente_db=# SELECT * from users;
Can't get past the 3rd step with community script , looked around couldn't find any clues.:
ente-setup
=== Ente First-Time Setup ===
Enter your account email: sissy@mail.com
Step 1/4: Register your account
Open the web UI: http://192.168.8.103:3000
Create an account with: sissy@mail.com
Make sure you click 'Don't have an account?' and complete the signup form.
Press ENTER after you submitted the signup form...
Step 2/4: Getting verification code from logs...
Your verification code: 415380
Enter this code in the web UI to complete registration.
Press ENTER after you verified the code in the web UI...
Step 3/4: Looking up user and whitelisting admin...
Warning: User 'sissy@mail.com' not found in database.
Make sure registration was completed successfully.
=== Setup incomplete ===
After completing registration, run ente-setup again.
root@ente:~#
verified and uploaded an image, but it says user not found in database... if i list all users in the database they are listed...
root@ente:~# su - postgres
Ente LXC Container - DEV Repository
WARNING: This is a DEVELOPMENT version (ProxmoxVED). Do NOT use in production!
OS: Debian GNU/Linux - Version: 13
Hostname: ente
IP Address: 192.168.8.103
Repository: https://github.com/community-scripts/ProxmoxVED
postgres@ente:~$ psql -d ente_db
ente_db=# SELECT * from users;
The issue here is the same. I started the command: "ente-upgrade-subscription user@example.com" with my added mail-address and there has been an SQL error that "email" is not a field in the table, if I remember correctly. I deleted the Container in the meantime.
OT:
Its actually amazing how unnecessarily bad ente is for automation. Something or the other keeps changing in Ente which breaks the script. Honestly, I'd recommend anyone trying to integrate Ente to just move to Immich, at least its stable and mostly reliable.
Even if you get Ente working, updating it down the line will definitely be a pain. Ente is open source just for the sake of it (to instil trust and stuff like that). Their main focus is their Business and so improving the self-host stack and making it simpler isn't their top priority.
✖️ in line 189: exit code 1 (General error / Operation not permitted)
→ yarn install
--- Last 20 lines of log ---
go: downloading github.com/gogo/protobuf v1.3.2
[2026-06-12 16:18:30] [OK] Built Museum
[2026-06-12 16:18:30] [INFO] Generating Secrets
[2026-06-12 16:18:31] [OK] Generated Secrets
[2026-06-12 16:18:31] [INFO] Installing MinIO
Added local successfully.
Bucket created successfully local/b2-eu-cen.
Bucket created successfully local/wasabi-eu-central-2-v3.
Bucket created successfully local/scw-eu-fr-v3.
[2026-06-12 16:18:44] [OK] Installed MinIO
[2026-06-12 16:18:44] [INFO] Creating museum.yaml
[2026-06-12 16:18:44] [OK] Created museum.yaml
[2026-06-12 16:37:00] [INFO] No URL provided
[2026-06-12 16:37:00] [OK] using local IP: http://192.168.178.46:8080
[2026-06-12 16:37:00] [INFO] No URL provided
[2026-06-12 16:37:00] [OK] using local IP: http://192.168.178.46:3002
[2026-06-12 16:37:00] [INFO] Building Web Applications
This project is configured to use npm because /opt/ente/web/package.json has a "packageManager" field
[2026-06-12 16:37:01] [ERROR] in line 189: exit code 1 (General error / Operation not permitted)
[2026-06-12 16:37:01] yarn install
📋 Full log: /root/.install-2a62861f.log
✖️ Installation failed in container 111 (exit code: 1)
Activity
MickLesk commentedon Sep 12, 2025
Despite self-hosting (if I haven't done anything wrong), there is a 10GB limit on photos. Wtf? @community-scripts/contributor
CrazyWolf13 commentedon Sep 12, 2025
@MickLesk a quick google search led me to this: ente/ente#2193
MickLesk commentedon Sep 12, 2025
Wtf 😄
CrazyWolf13 commentedon Sep 12, 2025
I think maybe because it's literally the exact source code of their hosted variant :D
tremor021 commentedon Sep 12, 2025
ente admin update-subscription -a <admin-user-mail> -u <user-email-to-update> --no-limitdramikei commentedon Oct 26, 2025
Hi, is this being worked on?
I am willing to contribute if theres a draft PR/branch etc :)
MickLesk commentedon Oct 26, 2025
Its already in this Repo, but not done. Currently Not worked on
dramikei commentedon Oct 26, 2025
Went over the install scripts and made a list of things that are pending in order to get a clean installation:
NEXT_PUBLIC_ENTE_ENDPOINTandNEXT_PUBLIC_ENTE_ALBUMS_ENDPOINTenv variables. Currently we set them ashttp://localhost:8080andhttp://localhost:3002respectively. This wont work, since these URLs are used by the Frontend when accessed by a browser. They need to be the IP of the LXC containers or the public URL for the backend./var/www/ente/apps/*directory manuallyI feel, we can get Ente working quite easily, @MickLesk has done a lot of the hard work already, there are a few quirks which we cannot resolve unless Ente team improves the self-hosted user experience like allows admin user creation via ente-cli, or by creating a default admin on museum setup. Maybe even a seed-data SQL script would be helpful. Without which we cant ensure a smooth unattended installation experience (which i would prefer tbh)
dramikei commentedon Nov 4, 2025
FYI: made some progress in the script. will test and ensure everything works and then raise a PR.
Was travelling for a week, will work on the PR over this weekend.
dramikei commentedon Nov 22, 2025
@MickLesk Can you check the PR once? I'm facing a very weird issue where if I execute the script in default mode or advanced without verbose I am facing crashes randomly. Error message simply says:
"General error/ Operation not permitted"
If I install via Advanced settings and verbose mode, everything installs normally
I have attached screenshot in the PR (we can discuss the issue in the PR itself)
MickLesk commentedon Nov 22, 2025
The Script never finished, because i get Issues over Issues with ente
15 remaining items
sbisbilo commentedon Apr 2, 2026
Hello,
I just test the script, no error at all but only in step 4 in ente-setup
The subscription plan is still 10Gb
Is it possible to have the choice to not install MinIO as the project is not longer maintained to use RustFS for example?
Regards,
Sylvain
MickLesk commentedon Apr 2, 2026
The question you should ask in ente. Without minio no Upload possible
jwsp1 commentedon Apr 16, 2026
Installation fails. Seems like the mc client container tries to set the alias and perform operations before the minio server has fully started and is ready to accept connections?
MickLesk commentedon Apr 16, 2026
Ente is really one of the stupid Apps ever...
Reshuffle6524 commentedon Apr 18, 2026
Can't get past the 3rd step with community script , looked around couldn't find any clues.:
verified and uploaded an image, but it says user not found in database... if i list all users in the database they are listed...
WarezNT commentedon Apr 22, 2026
I have this issue to.
carsten-h commentedon Apr 23, 2026
The issue here is the same. I started the command: "ente-upgrade-subscription user@example.com" with my added mail-address and there has been an SQL error that "email" is not a field in the table, if I remember correctly. I deleted the Container in the meantime.
luky92 commentedon Apr 24, 2026
You need to use ente cli with admin account to set it to unlimited
dramikei commentedon Apr 25, 2026
OT:
Its actually amazing how unnecessarily bad ente is for automation. Something or the other keeps changing in Ente which breaks the script. Honestly, I'd recommend anyone trying to integrate Ente to just move to Immich, at least its stable and mostly reliable.
Even if you get Ente working, updating it down the line will definitely be a pain. Ente is open source just for the sake of it (to instil trust and stuff like that). Their main focus is their Business and so improving the self-host stack and making it simpler isn't their top priority.
all my personal opinion btw.
abjeroen commentedon Jun 12, 2026
Error log on running script on shell. Hope this helps!
Enter the public URL for Ente backend (e.g., https://api.ente.yourdomain.com or http://192.168.1.100:8080) leave empty to use container IP:
✔️ using local IP: http://192.168.178.46:8080
✔️ using local IP: http://192.168.178.46:3002
✖️ in line 189: exit code 1 (General error / Operation not permitted)
→ yarn install
--- Last 20 lines of log ---
go: downloading github.com/gogo/protobuf v1.3.2
[2026-06-12 16:18:30] [OK] Built Museum
[2026-06-12 16:18:30] [INFO] Generating Secrets
[2026-06-12 16:18:31] [OK] Generated Secrets
[2026-06-12 16:18:31] [INFO] Installing MinIO
Added
localsuccessfully.Bucket created successfully
local/b2-eu-cen.Bucket created successfully
local/wasabi-eu-central-2-v3.Bucket created successfully
local/scw-eu-fr-v3.[2026-06-12 16:18:44] [OK] Installed MinIO
[2026-06-12 16:18:44] [INFO] Creating museum.yaml
[2026-06-12 16:18:44] [OK] Created museum.yaml
[2026-06-12 16:37:00] [INFO] No URL provided
[2026-06-12 16:37:00] [OK] using local IP: http://192.168.178.46:8080
[2026-06-12 16:37:00] [INFO] No URL provided
[2026-06-12 16:37:00] [OK] using local IP: http://192.168.178.46:3002
[2026-06-12 16:37:00] [INFO] Building Web Applications
This project is configured to use npm because /opt/ente/web/package.json has a "packageManager" field
[2026-06-12 16:37:01] [ERROR] in line 189: exit code 1 (General error / Operation not permitted)
[2026-06-12 16:37:01] yarn install
📋 Full log: /root/.install-2a62861f.log
✖️ Installation failed in container 111 (exit code: 1)
✔ Installation log: /tmp/install-2a62861f-combined.log
Error: General error / Operation not permitted
What would you like to do?
MickLesk commentedon Jun 12, 2026
Ente May will never come to our Scripts.