What's coming in 9.1
-
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
"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.
-
-
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 .
@girish is 9.1 stable already? Had another Cloudron that just updated by itself via cron
-
went smooth - except SFTP+
2026-03-07T10:42:32.173 ERR error initializing data provider: failed to connect touser=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:8080several restarts.
-
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 ?
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
-
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
-
@msbt 9.12 ?
-
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.
-
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.
-
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
I still get the "This update is a pre-release and not considered stable yet. Please update at your own risk." warning:
-
@timconsidine 9.1.3 is being rolled out . The upgrade path will be straight from 9.0.17 to 9.1.3
I still get the "This update is a pre-release and not considered stable yet. Please update at your own risk." warning:
@jdaviescoates that's the correct behavior. it's being rolled out in phases. are you expecting something else?
the alternate message here would be "This update is being rolled out." but given our small team size, we want something deterring people from all updating at once.
-
@jdaviescoates that's the correct behavior. it's being rolled out in phases. are you expecting something else?
the alternate message here would be "This update is being rolled out." but given our small team size, we want something deterring people from all updating at once.
-
Hello @murgero
Currently, we use the message
This update is a pre-release and not considered stable yet. Please update at your own risk.in two cases.Case 1:
What the message states exactly.
The update is pre-release and not considered stable yet.Case 2:
We also use the same message when we are rolling out the finished update to lower the load so not all systems automatically update at the same time.
DDoS protection against ourselves and to catch regressions that we might have missed early with fewer instances effected.
In Case 2, the automatic update would still trigger at some point when it is your systems turn to update.When we post the announcement in the Forum that e.g.: 9.1 is released, case 2 is in effect, but the message is still the same.
I understand the confusion here, and we will improve the message in this case to reflect what is actually happening.
We simply did not get to it, yet.
Apologies for the confusion, we will improve this in the future! -
I upgraded from 9.0.17 to 9.1.3 yesterday and everything went smooth as butter! Thanks to the Cloudron team for the awesome work!
-
Hello @murgero
Currently, we use the message
This update is a pre-release and not considered stable yet. Please update at your own risk.in two cases.Case 1:
What the message states exactly.
The update is pre-release and not considered stable yet.Case 2:
We also use the same message when we are rolling out the finished update to lower the load so not all systems automatically update at the same time.
DDoS protection against ourselves and to catch regressions that we might have missed early with fewer instances effected.
In Case 2, the automatic update would still trigger at some point when it is your systems turn to update.When we post the announcement in the Forum that e.g.: 9.1 is released, case 2 is in effect, but the message is still the same.
I understand the confusion here, and we will improve the message in this case to reflect what is actually happening.
We simply did not get to it, yet.
Apologies for the confusion, we will improve this in the future!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login