Cloudron Forum

timconsidine

Appreciate that mail is the focus of 9.2, but maybe you can sneak in a minor enhancement to Notifications :
From :
'Grafana at grafana.appx.uk updated to package version 2.5.1'
To :
'UPDATED Grafana at grafana.appx.uk to package version 2.5.1'
Speeds user review of notifications

timconsidine

Cloudron Team : I am not clear whether cloudron 3.24.0 used a different upstream base 3.1.0 to previous, but my impression is not. So the issue is in cloudron v3.24.0 ? Can it be fixed ?

timconsidine

Never had a problem with Umami before.
I had it set at 2Gb RAM which is a healthy amount for this kind of app (even maybe high).
Auto-upgrade to Cloudron v3.24.0 immediately brought repeat OOM
Increased it - reluctantly - to 3Gb.
Still crashing.

Checked redid for umami - running at 15% (40/256) - restarted it anyway.

Now umami is not responding.

Anyone else seeing this ?
Don't see any relevant GitHub issues for upstream 3.1.0

Lanhild

@james Done.

Lanhild

@robi Yes

Cloudron Container Registry 2.6.0 (registry 3.1.0)

Lanhild

@nebulon

I have another Cloudron server for which I did the upgrade too. Though, it didn't fix it for this one.

No outstanding errors in cloudron-support's output.

I'm pretty much at a dead-end here

timconsidine

@LoudLemur well done, sounds like you have had fun (!).

I'm not clear. You mentioned your production system - is that your own build or using my ALPHA community app ? Or you already cloned/fixed mine ?

If the latter, I can try to make changes as you describe. But I am in the middle of a couple of big projects, so it won't be immediate.

If timing is an issue, you might want to clone/fix and publish your own repo/community app.

timconsidine

I thought I was imagining it, but fairly certain that I am not.

Working on an app using CloudronVersions to publish, suddenly the app would not update in the Cloudron dashboard.
CloudronVersions.json is ~1600 lines long, from 0.0.1 to 0.7.5, jumping a few so about 60 versions
on last update CloudronVersions.json "lost" versions 0.7.2, 0.7.3 and 0.7.4 (and who knows what from earlier in the chain), so app running last version 0.7.4 would not find/recognise 0.7.5 as an upgrade
fixed by deleting versions 0.0.1 through 0.7.0 to shrink the file, copying 0.7.1 to 0.7.4 and manually editing values
app then says 'oooo, I see I am on 0.7.4 and found 0.7.4', and allows me to upgrade to latest 0.7.5
my build cycle is automated, I never touch CloudronVersions.json

Maybe lazy layman's diagnosis : some CLI bug in cloudron versions add loses content in Versions while adding a new one. Triggered by length limit or buffer constraint ?

Not a problem as such, as I now know how to fix it.
Surfacing this in case others come across it, maybe Cloudron team can check it when no other pressing tasks.

girish

Can you explain what issues you want to fix before building an image? Are you referring to the CloudronVersions.json or CloudronManifest.json ?

andreasdueren

@ekevu123 Cool app, toying with it right now. One observation:

when trying to connect to my nextcloud calendar, it connects and recognizes the different calendars but when I press Add integration, it returns Base url Must be a valid HTTP or HTTPS URL (e.g., https://example.com) nonetheless.

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

Cloudron Forum

AppDev

Posts

Member List