Cloudron App Packagers
@mrchrisjones Yes, this looks like a CORS issue. Have you checked the upstream documentation? I'm a bit surprised you got Cloudflare R2 working. I thought I remember trying it back when I packaged this and there were compatibility issues.
Personally I'm using replication with B2, Hetzner and Scaleway (in this order).
girish said:
mail: allow cloudron email to be used as a mail relay. this will allow one cloudron to relay emails via another cloudron without having to disable mail from validation.
I have made two big changes here. The domain level flag to disable mail from validation is now gone. It is now instead per mailbox. The migration logic will migrate the domain level settings into mailbox level setting.
In general, you should never need the above flag and it's only there because we had the global flag. There is a now a new feature called SMTP relay. You can create tokens which you put in external apps/services to send mail via your server.
@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.
@sponch still a long way out since we are just implementing the features. I can provide a date, when we are at least done implementing them 
But we are moving very quickly 
girish said:
mail: housekeeping task. we want to move away from usage of ldap for auth entirely. many of the node ldap modules have become unmaintained
mail: housekeeping task. the mail database is partly in box code and partly in mail server. have to move everything into mail server. this will help us implement backup/restore of mail nicely as well.
Both done now Got rid of LDAP entirely from the mail server.
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:
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 before I spin up a new test instance to try to reproduce this, could you please respond to these questions:
Hi,
I noticed that on my Cloudron (9.2.0) the current version is not shown:
I can reproduce this on my.demo.cloudron.io as well by installing a fresh surfer app.
@marcusquinn what can i say it's in the never ending list of platform features to add.
@robi darn - thanks for the alert - fixed - reload page and click download again 
