Ente for cloudron, help for testing wanted.
-
@andreasdueren omg totally forgot to answer. Installation and testsync were okay. However I deleted the app after the test and hope to get an official cloudron app soon.
@sponch Honestly not sure if they will ever support it. Don't seem to be keen on apps which need s3. This has been incredibly stable for me though if it's any reassurance. And switching to a cloudron package should also be no issue should they adopt it.
-
Updated Ente Package: andreasdueren/ente-cloudron:0.6.2
️ New: Configurable email footer
Three new fields in the Cloudron app config UI:- Organization name — replaces the bare URL in email footer link text
- Support email — adds "Questions? email@example.com" to the footer
- Support URL — adds a "Get help" link (fallback if no support email set)
All fields are optional. If left blank, the footer falls back to showing your instance URL as before.
-
Updated Ente Package:
andreasdueren/ente-cloudron:0.6.3
️ Fix: startup.log no longer grows unbounded
The startup log was being appended across every restart, growing to 4-5 GB and causing very slow backups. It is now truncated on each startup — only the current session's logs are kept. Backups will be significantly faster from the next restart onward.Upstream changes (ente-io/ente):
• 792f28c: README: add Locker Obtainium and GitHub release links
• 9810269: [mob][locker] Prevent duplicate default collections during signup
• 26549fc: [mob][photos] VectorDB write index fix
• 686706b: Toggle to let ML run continuously
• 922784b: Internal toggle to let ML run continuously without interruption -
@sponch Honestly not sure if they will ever support it. Don't seem to be keen on apps which need s3. This has been incredibly stable for me though if it's any reassurance. And switching to a cloudron package should also be no issue should they adopt it.
@andreasdueren Isn't it possible to selfhost s3 thou (like Ceph, garage, seaweedFS), maybe they could support that way? Or do you think it is something else? and Thank you so much for u great work!
-
@andreasdueren Isn't it possible to selfhost s3 thou (like Ceph, garage, seaweedFS), maybe they could support that way? Or do you think it is something else? and Thank you so much for u great work!
-
I'd really like to give this a go on Cloudron but I just can't get it to install and function. When I go and create a new user account on the Ente web interface in spins on generating encryption keys for quite a while and then just says "something went wrong." Any thoughts?
-
I'd really like to give this a go on Cloudron but I just can't get it to install and function. When I go and create a new user account on the Ente web interface in spins on generating encryption keys for quite a while and then just says "something went wrong." Any thoughts?
@mrchrisjones before I spin up a new test instance to try to reproduce this, could you please respond to these questions:
- did you set up s3 compatible storage?
- And if so, which one?
- Also, is there anything in the logs that pops up when you try to register?
- what browser are you using
- if you are on a Mac, do you have Lockdown Mode enabled?
- could you share here or in a dm the domain so I can test the login flow my end?
-
I’d first check the app logs while reproducing the signup failure, because the “generating encryption keys” message is likely just where the frontend fails after submitting the generated keys to the backend.
Can you run this while trying to create the account again?
cloudron logs --app <your-ente-app-domain> -fAlso please open the browser DevTools → Network tab and check which request fails after “generating encryption keys.” I’d expect a failed request to
/api/users...or a mail/verification-related endpoint. The HTTP status and response body there would be very useful.The most likely causes are:
- Cloudron mail/sendmail is failing, so Ente can’t send the verification email.
- The frontend is calling the wrong API origin.
- S3 config is incomplete or invalid.
You can also check the startup config log with:
cloudron exec --app <your-ente-app-domain> -- tail -n 200 /run/ente/logs/startup.logIf the logs mention SMTP/mail errors, this is probably a Cloudron mail configuration issue rather than an encryption-key generation issue.
-
@mrchrisjones before I spin up a new test instance to try to reproduce this, could you please respond to these questions:
- did you set up s3 compatible storage?
- And if so, which one?
- Also, is there anything in the logs that pops up when you try to register?
- what browser are you using
- if you are on a Mac, do you have Lockdown Mode enabled?
- could you share here or in a dm the domain so I can test the login flow my end?
@mrchrisjones before I spin up a new test instance to try to reproduce this, could you please respond to these questions:
- did you set up s3 compatible storage?
- And if so, which one?
- Also, is there anything in the logs that pops up when you try to register?
- what browser are you using
- if you are on a Mac, do you have Lockdown Mode enabled?
- could you share here or in a dm the domain so I can test the login flow my end?
Hi there, yes I setup Backblaze B2 storage. I am on a Mac, no lockdown mode. Only thing I notice is that it hangs on /api/users/otp but I am unable to trace the logs with the commands you shared as cloudron is not a found command. This is on a Cloudron install that's less than 24 hours old. The email is setup with an external smtp relay and sends emails with no error. In one of the Ente logs I do have access to I see the following error, looks like its hardcoded to some sort of mail server IP that I don't recognize.
ERRO[18480]handler.go:51 Error Request failed error= --- at /ente/server/pkg/api/user.go:45 (UserHandler.SendOTT) --- --- at /ente/server/pkg/controller/user/userauth.go:134 (UserController.SendEmailOTT) --- --- at /ente/server/pkg/controller/user/userauth.go:580 (emailOTT) --- --- at /ente/server/pkg/utils/email/email.go:216 (sendViaSMTP) --- --- at /ente/server/pkg/utils/email/email.go:239 (sendMailWithEncryption) --- Caused by: dial tcp 172.18.0.1:2465: connect: connection timed out Caused by: failed to establish TLS connection -
I followed the instructions and did just the required S3 config before I tried creating an account, but nothing I do works.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login