Ente
-
I got photos and auth working. What still needs to be done:
- Make CLI work to increase storage quota
- Set up OTT to be sent via E-Mail
- Implement option to use multiple s3 backends for redundancy
- Check Accounts app
@andreasdueren
hope this will make it to cloudron. -
I'm hitting a road block with this package. @girish any advice?
Go's
smtp.PlainAuth(used by Museum) refuses to send credentials (the TOTP) over unencrypted connections for security. Cloudron's sendmail on port2525requires authentication but is unencrypted, causing the error: "unencrypted connection".What I Tried:
1: Port
2525without auth →550 "cannot deliver mail"(requires auth)
2: Port2525with auth → "unencrypted connection" (PlainAuth rejects)
3: Port2587withSTARTTLS→ Certificate validation fails (x509: certificate is valid for*.tld.com, notmail)
4: Port2465withTLS→ Same certificate issue -
@andreasdueren oh this is a general problem with Go apps which don't want to send email to servers without valid TLS certificates . You can set
requiresValidCertificateas an option forsendmailaddon in the manifest . See the fider and pocketbase packages which use this. Currently, this flag needs Cloudron 9. -
@andreasdueren oh this is a general problem with Go apps which don't want to send email to servers without valid TLS certificates . You can set
requiresValidCertificateas an option forsendmailaddon in the manifest . See the fider and pocketbase packages which use this. Currently, this flag needs Cloudron 9.@girish thanks I'll try that out
-
E-Mail sending works. But I'm exploring how I can use a subdomain setup because the /auth app still returns 401 (“Session expired”) because the auth frontend isn’t picking up the access token the photos/accounts app stored, so the request only carries X-Auth-Token and gets treated as anonymous.
Upstream solves this by using separate subdomains (photos., accounts., auth.*) so each app stores its own token bundle. On my single-origin deployment (https://ente.tld.com/...), the auth app never sees the right token, hence the recurring 401s.
-
E-Mail sending works. But I'm exploring how I can use a subdomain setup because the /auth app still returns 401 (“Session expired”) because the auth frontend isn’t picking up the access token the photos/accounts app stored, so the request only carries X-Auth-Token and gets treated as anonymous.
Upstream solves this by using separate subdomains (photos., accounts., auth.*) so each app stores its own token bundle. On my single-origin deployment (https://ente.tld.com/...), the auth app never sees the right token, hence the recurring 401s.
@andreasdueren would adding aliases help with this?
-
@andreasdueren would adding aliases help with this?
@robi Yes I'm currently using aliases but those can't be automatically be set up upon install so the user will need to manually add
family,albums,cast,authandaccountssubdomain aliases. -
@robi Yes I'm currently using aliases but those can't be automatically be set up upon install so the user will need to manually add
family,albums,cast,authandaccountssubdomain aliases.@andreasdueren I know we have a modal from an App Store install where these are prefilled, but you are right it’s not automated.
-
https://forum.cloudron.io/post/114641
Please help me test this package
-
@andreasdueren haven't found time to test ente but for multiple domains, Cloudron has two concepts - multiDomain (https://docs.cloudron.io/packaging/manifest/#multidomain) and httpPorts (https://docs.cloudron.io/packaging/manifest/#httpports).
httpPortsis best suited when the domain names are to be known in advance (for example , minio's API subdomain).multiDomainis when an app can handle many subdomain but it's not needed for the app to work - wordpress multidomain concept, espocrm customer portals etc. -
@andreasdueren haven't found time to test ente but for multiple domains, Cloudron has two concepts - multiDomain (https://docs.cloudron.io/packaging/manifest/#multidomain) and httpPorts (https://docs.cloudron.io/packaging/manifest/#httpports).
httpPortsis best suited when the domain names are to be known in advance (for example , minio's API subdomain).multiDomainis when an app can handle many subdomain but it's not needed for the app to work - wordpress multidomain concept, espocrm customer portals etc.