Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install

AppDev

Private

Cloudron App Packagers

Posts


  • Ente for cloudron, help for testing wanted.
    andreasduerenA 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.

    App Packaging & Development

  • What's coming in Cloudron 10
    girishG girish

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

    Announcements

  • What's coming in Cloudron 10
    girishG girish

    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.

    Announcements

  • Ente for cloudron, help for testing wanted.
    andreasduerenA 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.

    App Packaging & Development

  • Ente for cloudron, help for testing wanted.
    andreasduerenA 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?
    App Packaging & Development

  • Surfer NewVersionIsNotSet
    fbartelsF fbartels

    Hi,

    I noticed that on my Cloudron (9.2.0) the current version is not shown:

    84299333-62e8-4d2d-a720-f6ff8dfc27fd-image.jpeg

    I can reproduce this on my.demo.cloudron.io as well by installing a fresh surfer app.

    Surfer

  • NostrVPN
    girishG girish

    @marcusquinn what can i say 🙂 it's in the never ending list of platform features to add.

    Discuss

  • BarDock - minimal app switcher for Mac
    timconsidineT timconsidine

    @robi darn - thanks for the alert - fixed - reload page and click download again 🙏

    Off-topic

  • Can we add a pdf-engine to the installed pandoc?
    girishG girish

    @dcwalk I already added that package - https://git.cloudron.io/packages/n8n-app/-/commit/011e4e46090dc467aef8e24bbd8b75932bd0f0f1 . Are we missing something else?

    N8N

  • Database 'main' is using PostgreSQL 16.11, but this version of GitLab requires PostgreSQL 17
    girishG girish

    Yeah, we noticed this in our GitLab instance too. We will update Postgres to 17 in Cloudron 10 but for now you can ignroe the warning. Alternately, roll back and wait for Cloudron 10 .

    GitLab

Member List

girishG girish
P pathab
rmdesR rmdes
vitetjV vitetj
andreasduerenA andreasdueren
canadaduaneC canadaduane
njN nj
T TheNils
eyecreateE eyecreate
LanhildL Lanhild
W walski
KubernetesK Kubernetes
timconsidineT timconsidine
R random_eric
B bram
jeauJ jeau
marioM mario
eriktadE eriktad
BrutalBirdieB BrutalBirdie
mehdiM mehdi
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search