What's coming in 9.1

[girish]

@msbt said:

Uhh what? One of my production Cloudrons already got updated automatically 3 days ago?!

that seems quite unlikely Can you check who was the initiator of the update in the eventlog? The 'source' field will be 'cron' or some real user .

[msbt]

@girish maybe I'm just the lucky one, that happened before on other machines with other versions:

It's a bit tricky, because that specific Cloudron has a bunch of custom apps which are best stopped before updating/rebooting. I remember a thread about release channels or separate app updates from Cloudron updates, is that somewhere on the roadmap?

Edit: it says "unstable": false in the tasks json

[girish]

App updates are already separate from Cloudron updates. But maybe you mean the separation of the automatic update flag , will get to that in the coming releases .

[msbt]

Yes that's what I meant, auto updates for apps but not the platform. Awesome!

[ruihildt]

Two small issues:

• "Dashboard" repeated twice in the tab title
• When installing an app, trying to add an existing contact, the usernames don't show

[ruihildt]

And a third more serious error

See: https://forum.cloudron.io/topic/15181/gandi-dns-failing-to-be-set-using-either-api-token-or-pat

[joseph]

@ruihildt said:

"Dashboard" repeated twice in the tab title

Is your Cloudron name "Dashboard" ? See Appearance -> Branding. Can you reproduce on the demo server?

When installing an app, trying to add an existing contact, the usernames don't show

Can reproduce.

[ruihildt]

@joseph said:

Is your Cloudron name "Dashboard"

It was^^"

[msbt]

@girish is 9.1 stable already? Had another Cloudron that just updated by itself via cron

[murgero]

@msbt Full send I guess?

[girish]

@msbt yes, we have started the roll-out.

[sponch]

went smooth - except SFTP+
2026-03-07T10:42:32.173 ERR error initializing data provider: failed to connect to user=usercdd5780385b84f3482b83f6a184b36c9 database=dbcdd5780385b84f3482b83f6a184b36c9: hostname resolving error: lookup postgresql on 127.0.0.53:53: read udp 127.0.0.1:43967->127.0.0.53:53: read: connection refused
Mar 07 11:42:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.18.18:8080
Mar 07 11:42:42 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.18.18:8080

several restarts.

[timconsidine]

Cloudron v9.1.3 is available
This update is a pre-release and not considered stable yet. Please update at your own risk.

Which version is being rolled out ?

[girish]

@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3

[msbt]

@girish well...

[timconsidine]

@msbt 9.12 ?

[msbt]

@timconsidine exactly

[nebulon]

Oh those cloudrons seem to have fetched the update info previously and didn't catch the jump directly to 9.1.3. Going first via 9.1.2 is harmless though.

[girish]

I think in @msbt 's case the Cloudron already updated to 9.1.x unexpectedly (from a previous post). So, this is expected. For those on 9.1.x already, it is correct to update 9.1.0 -> 9.1.1 -> 9.1.2 -> 9.1.3 . Basically, we can't and don't test all the possible code paths when we make new releases. 9.0.17 -> 9.1.3 was explicitly tested since most people are on 9.0.17.

[jdaviescoates]

@girish said:

I think in @msbt 's case the Cloudron already updated to 9.1.x unexpectedly (from a previous post).

But did you ever get to the bottom of why that happened?