Ente for cloudron, help for testing wanted.

[andreasdueren]

@Muhanand Definitely possible. But this app just by nature requires a more sophisticated manual setup.

[mrchrisjones]

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?

[andreasdueren]

@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?

[andreasdueren]

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> -f

Also 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:

1. Cloudron mail/sendmail is failing, so Ente can’t send the verification email.
2. The frontend is calling the wrong API origin.
3. 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.log

If the logs mention SMTP/mail errors, this is probably a Cloudron mail configuration issue rather than an encryption-key generation issue.

[mrchrisjones]

@andreasdueren said:

@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

[mrchrisjones]

I followed the instructions and did just the required S3 config before I tried creating an account, but nothing I do works.

[andreasdueren]

@mrchrisjones That pretty much points to failing on email/OTP delivery, not on Backblaze B2 or browser encryption key generation.

172.18.0.1 looks to be Cloudron’s internal mail relay address. Ente/Museum is trying to send the signup OTP email through Cloudron’s mail addon at 172.18.0.1:2465, and that connection is timing out:

dial tcp 172.18.0.1:2465: connect: connection timed out

So /api/users/otp hangs because Museum cannot reach the SMTP relay.

You don’t need the cloudron command on your Mac. In the Cloudron web UI, open the Ente app, then use the app’s Terminal/Console and check:

env | grep CLOUDRON_MAIL

If the internal Cloudron SMTPS relay is unreachable, you can try overriding Museum’s SMTP config directly in:

/app/data/config/museum.override.yaml

I just pushed a package update which supports these changes. Please update to the latest version (0.6.100). The new image should include the ENTE_SMTP_* support.

Example for an external SMTP server using implicit TLS:

smtp:
  host: "smtp.example.com"
  port: "465"
  username: "smtp-user"
  password: "smtp-password"
  email: "ente@example.com"
  sender-name: "Ente"
  encryption: "tls"

Then restart the Ente app.

Important: Ente/Museum supports tls/ssl for implicit TLS, or no encryption. It does not support STARTTLS, so port 587 usually will not work unless the relay also accepts plain SMTP there. For most external relays, use port 465 with encryption: "tls".

The Cloudron app email UI may not show much here because apps normally talk to Cloudron’s internal mail relay, and Cloudron then relays externally. The log you shared shows the app cannot connect to that internal relay.

[mrchrisjones]

Thanks, that SMTP override seems to have done the trick! I appreciate the quick response. Now to figure out why uploading photos doesn't work... any ideas on why Backblakze B2 wouldn't work? The logs in ente don't really provide a ton of info. And earlier I meant the cloudron command doesn't work on my cloudron terminal, not on my Mac directly. I tried it inside of the app terminal, the web cloudron terminal and even ssh into the device with no luck.

[mrchrisjones]

Ok let me add Cloudron R2 to the list as well. I'm unable to get anything to upload with that bucket either. Any chance there is an override for those settings too the same way SMTP was handled?

[mrchrisjones]

Ok I got R2 to work, needed to set the CORS rules just to be able to upload files, which the documentation seemed to only recommend for certain parts of Ente and not for the uploading functionality. I assume the Backblaze B2 issue is related to CORS as well.