Fórum Cloudron Forum

@mpevhgnuragistes What browser are you using when you upload the logo file? This is most likely due to enhanced tracking protection being set against your Cloudron server, including HTML5 Canva and/or WebGL being blocked in your browser.

@aartjansen don't you see a retry button in the UI?

Hello @umnz Yes, this means that the app is a new addition and considered unstable. You can use it, but it could be that a future update might break something.

[image: image.jpeg]

Thank you for your help, I'll try this!

Hello @umnz App Proxy can still be stopped with the cloudron cli. But that the UI is missing the controls might be a regression. Thanks for reporting, we will look into this.

Hello @milohiss @milohiss said: Are maintenance emails sent only when a notice is first created? Can its dashboard timestamp change without another email being sent? Yes to both, and that is exactly what you are seeing. Email fires when the notification is first created, or when an already-acknowledged notice is re-raised. An unacknowledged notice that keeps re-pinning gets its creationTime bumped every run and the dashboard renders that field and sorts by it, so it looks brand-new at the top of the bell while no mail is generated. The August email was the original send, nothing has been "missed" since, by design. @milohiss said: What read-only diagnostic can distinguish expected suppression of repeat notifications from a failure to generate or send the email? In the box.log you could find lines like: mailer: Email "..." sent to ... for a successful send Error sending Email ... for a real failure notifications: add: for a notification being added logged only on insert not on update @milohiss said: All available email notification categories are now enabled. Does this cover every new bell notification? If not, which are dashboard-only? They cover every notification that can produce an email. But several bell notices have no mailer and are dashboard-only and these are: cloudronInstalled, cloudronUpdated, ubuntuUpdate (for EOL warnings like Ubuntu 20), mailStatus (Email configuration error), domainConfigCheckFailed, appUpdateCheckFailed Maybe this is something we could improve.

Fixed. We display inactive users separately now at the bottom of the users list.

Oh so you guys did change the pricing. Are we grandfathered at the account level or at the existing plan level? Nevermind. The answer is a few posts above this. (I didn't originally read that far)

I can see my VPS used 7.47gb/8gb lastnight during the backup. The fact is, I haven't changed anything, and it was not consuming all this RAM on Cloudron 9.X

Hello @dsp76 I have just tested this flow. User with TOTP and passkey configured. Attempt login with username and password: opens the passkey context of bitwarden and shows only the passkey for this user clicking the passkey login success Attempt login with username and password: opens the passkey context of bitwarden closing the bitwarden context without selecting the passkey, falls back to device passkey cancel that as well UI prints Failed to login with passkey, now I can input a TOTP enter TOTP and pressing Login login success Attempt login with passkey: bitwarden context opens showing all passkeys available for this domain selecting my passkey for the user login success Does this flow not work with 1password? Or do you think the flow should be changed so that if multiple 2FA options are configured for a user, the UI asks the user which one to use? Similar to our NodeBB forum when having TOTP and Passkey configured? [image: image.jpeg]